-
Posts
189 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Skittles
-
GF-Display, Doesn't hurt to ask, right?
Skittles replied to Skittles's topic in FSUIPC Support Pete Dowson Modules
You trying to get me killed! :lol: Just kidding. Thank you very much for your time and I hope you had a good visit, with your family. Welcome back to retirement work. -
Post deleted.
-
GF-Display, Doesn't hurt to ask, right?
Skittles replied to Skittles's topic in FSUIPC Support Pete Dowson Modules
Sorry, I forgot all about PMSounds. I didn't know I should have Pitot heat on during flight, thanks. If I remember correctly, Anti-ice/De-ice has no affect in FS. I thought I read that somewhere. Can you confim or deniy? Regards, Joe -
PROBLEM ABOUT OFFSETS ON FS2004
Skittles replied to vercellino_marco's topic in FSUIPC Support Pete Dowson Modules
Have you also considered updating FSUIPC to 3.48? I'm not sure about the 3.4.0.0 -
VB/FSUIPC users or Gurus, Question to ask...
Skittles replied to High-Octane's topic in FSUIPC Support Pete Dowson Modules
Then I suppose only Mr. Dowson could help. I created a program that had a radar scope and little symbols for various ships using nothing but lines and circles. I had the same effect your describing. In this case, I never did find a solution. Sorry. Joe -
YES YOU CAN!!! 1. Open up FS/FSUIPC and assign the button you want to shift with SHFT-a. Also check the Repeat while held box. Click OK but do not close FS. 2. Open FSUIPC.ini (in the modules directory) and scroll down until you find Pxxx=Rx,0,K65,9 In my case the line was at the bottom and read... 101=R0,0,K65,9 3. Change K65 to K0 (that's a zero). Save the file. 4. Go back to FS/FSUIPC, Buttons tab and click the "Reload All Buttons" button. Now try it! Here's what we did. K65 means Keyboard and 65 is the numeric representation of the letter "a", not "A". By changing 65 to 0 (zero), we are assigning it as a Null character. So when you press the button, only the Shift is recognized. Thanks for the idea! Joe
-
VB/FSUIPC users or Gurus, Question to ask...
Skittles replied to High-Octane's topic in FSUIPC Support Pete Dowson Modules
I tinkered with the APX for speech, but didn't get the results I wanted. Also, I don't think this forum is the best place since the problem isn't with FSUIPC. I used to have a few links to VB programming sites. Let me look around again, and I'll update this post. Joe EDIT: Try this http://www.programmersheaven.com -
VB/FSUIPC users or Gurus, Question to ask...
Skittles replied to High-Octane's topic in FSUIPC Support Pete Dowson Modules
Are your graphics BMP or JPG? I've had the same problem. I used GIF or TGA and the shutters got a little better. I believe the problem is VB's ability to draw the graphics. I think it sometimes takes longer than 55ms to render, which is what's causing the shutter. GIFs and TGAs I guess render a little quicker than 55ms. In addition, I believe most of the shutter is caused by the fact that VB clears the image before drawing it again. I don't know of any other solution. Joe -
Offset 0898 Jetliner's N1
Skittles replied to High-Octane's topic in FSUIPC Support Pete Dowson Modules
Glad to be of help. -
Offset 0898 Jetliner's N1
Skittles replied to High-Octane's topic in FSUIPC Support Pete Dowson Modules
Okay, I think I understand now, this makes more sence in relation to the Factor Question. So you want to covert 0-16384 to 0-100? That's easy Percentage = InputValue / 163.84. This will give you the 0-100 percentage. To scale the 0-16384 to 0-100, use 16384/100=163.84. If you want to scale it to an RPM, let's say a max RPM of 2000, use 16384/2000=8.192 Is this what you're looking for? -
Offset 0898 Jetliner's N1
Skittles replied to High-Octane's topic in FSUIPC Support Pete Dowson Modules
If FSUIPC_Read(&H898, 2, VarPtr(N1Gauge), dwResult) Then If FSUIPC_Process(dwResult) Then Isn't something aupposed to be here??? End if End If Overall, this confuses me. If I understand correctly, you're checking to see IF... FSUIPC_Read(&H898, 2, VarPtr(N1Gauge), dwResult) is >0 but if so, you're then checking to see IF... FSUIPC_Process(dwResult) is > 0, but if so, there's nothing happening. N1Gauge = 0 ?? <--- Is that what it should be? N1Angle = N1Gauge This assigns a zero value to N1Gauge and then makes N1Angle also equal 0. If N1Gauge > 0.1 Then N1Angle = 0.1 Else If N1Gauge < 0.1 Then N1Angle = 200 End If So then why would you check to see if N1Gauge is > 0.1 when you just assigned it to zero. Also, N1Gauge would never be < 0.1. Zero is the lowest value that H898 returns. What exactly are you trying to accomplish? -
Offset 0898 Jetliner's N1
Skittles replied to High-Octane's topic in FSUIPC Support Pete Dowson Modules
I'm not sure what you mean by this. Are you creating a Visual Basic (VB) program? -
Hello again Mr. Dowson, I am having a wonderful time with GF-Display and I have an idea, but, it is outside your design intention. I'm not sure how receptive you'll be, but I just have to ask. Is it possible, and if so, would you consider adding a feature which would allow us to play a wav file or MP3 if a condition is true? Where do I get these crazy ideas? Well, I have a button assigned to Pitot Heat. I've written the code in such a manner where the LED will flash if I need to turn on the Pitot Heat based on the outside air temp. So I thought a little beeping sound would be nice as well. Hope you had a good vacation and Thanks for your time, Joe
-
I think FSUIPC 3.481 TEST is acting wierd. Before a GF-TQ6 change, I had my throttles set to control Engines 3 & 4 and it worked fine. I had turned my GF-TQ6 upside down to hide the USB cord and so all levers are at the same position when maxed, and this is what I'm getting. This is the result of Throttle 1 max which I believe to be correct. This is the result of Throttle 2 max which I believe to be incorrect. Are these displays correct. I would think that by increasing my Throttle 2, it would affect the 3 & 4 displays? In any case, it works correctly in FS2004.
-
Well, that's the trouble. It reflects more the state of the switch or lever -- its either zero or 16256. It doesn't appear to offer any intermediate values. Pete It doesn't really matter. It doesn't take as long for the rudders to transition as much as it does for the wings. I've added the appropriate code to my GFDisplay.ini file, and it works just fine. Thanks again, Joe
-
Well, I figure if it's not up or down, it's moving. So I assume it's in motion until the min or max value is reached.Thanks for the update! Joe
-
I agree completely. Your willingness to assist us is unsurpassed and your ability to take suggestion, if practical, and implement it rapidly is a very, very rare trait. With out you and your software, I believe, would diminish our flight simming experience. I sincerely thank you , Joe
-
The documentation states (at least how I understand it) is that I can only provide literal values. I don't know if this was supposed to work, but it does. I am once again tinkering with GFdisplay trying to get it to do all sorts of weird things it was not designed to do. This project has three LEDs lighting up according to Flaps position. (The Cessna only has three extensions so that's why I'm going with three) [GFT8.0] ;X0BE0 = Left Flaps Inicator ;X3BFA = Flaps Detent Increment L7=X0BE0 U16 >X3BFA L6=X0BE0 U16 >X3BFA *2 L5=X0BE0 U16 >X3BFA *3 So at the first position, L7 lights up. Second position, both L7 & L6 light up. Third position, all three light up.
-
GFDisplay Condition Limitations
Skittles replied to Skittles's topic in FSUIPC Support Pete Dowson Modules
Yep, that did the trick. :D You're awsome! Thanks. -
GFDisplay Condition Limitations
Skittles replied to Skittles's topic in FSUIPC Support Pete Dowson Modules
I've moved C15 into the Unit section for a direct comparison. When I shut it off, the LED goes out. So it seems that when a condition, within a condition, changes from true to false, it's somehow not getting noticed. Here's what I'm doing, only focusing on the Fuel Pump and Prop Pitch. 1. With the pump on and the pitch is max, the LED comes on. OK 2. Moving pitch to min, LED stays on. SHOULD GO OFF 3. Resave ini file. LED goes out. OK 4. Move pitch to max, LED goes on. OK 5. Turn Pump off, LED goes out. OK 6. Move pitch to min then turn pump on, LED goes on. SHOULD STAY OFF -
My overall purpose for this is to have an LED light up when the aircraft is properly configured for Flight. The manual for GFDisplay states I can have up to 8 true AND 8 False conditions on a line. I've setup all my conditions to be true. So I have trunicated lines by creating more condition lines. For example... [Conditions] 0=X2A48 F64 *100 =100 ; Left Wing Folded 1=!C0 X2A48 F64 *100 !=0 ; Left Wing in Motion 2=X2A48 F64 =0 ; Left Wing Extended 3=X2A50 F64 *100 =100 ; Right Wing Folded 4=!C3 X2A50 F64 *100 !=0 ; Right Wing in Motion 5=X2A50 F64 =0 ; Right Wing Extended 6=X3BA0 F64 *100 =100 ; Hook Extended 7=!C6 X3BA0 F64 *100 !=0 ; Hook Moving 8=X3BA0 F64 =0 ; Hook Retracted 9=X0AEC U8 =1 ; Aircraft has 1 Engine 10=X0AEC U8 =2; Aircraft has 2 Engines 11=X0AEC U8 =3; Aircraft has 3 Engines 12=X0AEC U8 =4; Aircraft has 4 Engines 13=X0366 U8 =1; A/C on ground 14=X3367 U8 =0; Doors closed 15=X3104 U8 =1; Fuel Pump On 16=X0894 U16 =1; Engine 1 Running 17=X092C U16 =1; Engine 2 Running 18=X09C4 U16 =1; Engine 3 Running 19=X0A5C U16 =1; Engine 4 Running 20=X0609 U8 =0; Piston Engine 21=X0609 U8 =1; Jet Engine 22=X0609 U8 =5; TurboProp Engine 23=X088E U16 >15000; Eng 1 Prop Pitch Full 24=X0926 U16 >15000; Eng 2 Prop Pitch Full 25=X09BE U16 >15000; Eng 3 Prop Pitch Full 26=X0A56 U16 >15000; Eng 4 Prop Pitch Full 27=X0890 U16 >12500; Eng 1 Fuel Mix Rich 28=X0928 U16 >12500; Eng 2 Fuel Mix Rich 29=X09C0 U16 >12500; Eng 3 Fuel Mix Rich 30=X0A58 U16 >12500; Eng 4 Fuel Mix Rich 31=C13 C14 C2 C5 C8 C15 =1;On Gnd, Door Closed, Wings Ext, Hook Ret, Pump On 32=C16 =1; Engine Running 33=C16 C17 =1; Both Engines Running 34=C16 C17 C18 =1; All 3 Engines Running 35=C16 C17 C18 C19 =1; All 4 Engines Running 36=C23 =1; Engine Prop Pitch Full 37=C23 C24 =1; Both Engines Prop Pitch Full 38=C23 C24 C25 =1; All 3 Engines Prop Pitch Full 39=C23 C24 C25 C26 =1; All 4 Engines Prop Pitch Full 40=C27 =1; Engine Fuel Mix Full 41=C27 C28 =1; Both Engines Fuel Mix Full 42=C27 C28 C29 =1; All 3 Engines Fuel Mix Full 43=C27 C28 C29 C30 =1; All 4 Engines Fuel Mix Full [GFP8.1] Needs=B E L3.1=!C13 =0 L3.2=C13 !C14 =1 Fslow L3.3=C31 C20 C9 C32 C36 C40 =1 L3.4=0 For my example, L3.3 has six conditions, however, C31 also has six conditions. This seems to be working... for the most part. When all conditions are met, The LED lights up. However, when I don't meet a condition (Turning off the Fuel Pump for example), the LED does not go out. Am I using L3.4=0 incorrectly? If I resave the GFDisplay.ini file, the LED goes out. And when I meet all conditions the LED does come back on, but when I don't meet the conditions, the LED does not go out. It's my understanding that if there are no lines where all conditions are true, processing will continue to the next line until it sees L3.4=0, which should turn off the LED. Please correct me if I'm wrong. I also understand that when a line has all true conditions, the remaining lines are skipped. So I know the importance of having thing in the correct order when applicable. I've checked and fiddled and re-checked. I just can't seem to find the problem. Thanks for your time, Joe
-
Yes.
-
66482 TOGGLE_WATER_RUDDERThe default aircraft, Cessna Caravan is a waterplane and has little rudders on the pontoons. I have another GFDisplay question though, I have a GF-T8 switch assigned to TOGGLE_GPS_DRIVES_NAV1 (66375) I have the LED working correctly, but when I throw another switch on the same T8, the indicator for the NAV/GPS switch goes blank. Is there something else I missed in the docs? Many Thanks, Joe
-
FDIII comes with a FSUIPC.DLL v3.07. So when you installed it, it replaces your newer version with an older one.
-
GFDisplay is kicking my butt.
Skittles replied to Skittles's topic in FSUIPC Support Pete Dowson Modules
Thanks Mr. Dowson, I did find my errors and corrected them before you posted. I keep troubling you with my stupid mistakes and I appologize. Thanks again for your help.