Skittles

I did, that's what this is... Also the same with 1.10 OK, I'll try that. The latest, but they've screwed up other stuff, so I'll look for an older one.

Previous version of... GFDisplay I assume since FSUIPC wouldn't be looking at x2B00? I wouldn't know if the problem lies with the bank angle (why would it) or the rate of turn, or even the rate of bank, but... Still using GFdisply 1222 and looking at the Compass I get the following results, 1. High rate of bank, GF46 updated regardless of bank angle or rate of turn. 2. Low rate of bank (1-2 degrees per 5 seconds), GF46 did not update until about 18-20degrees of bank angle. I think I remember you say that GFDisplay only executes a line when the offset value changes? Is it possible it also take into account the rate of change? ADDED Same thing with GFDisplay 1.10 ADDED Even while taxiing, GF46 did not change until I was turning more than about 2 degress per second. Wierd.

I meant priority, not affinity, sorry. I thought I could set the priority of GFDisplay using FSAutoStart but I was wrong, so I did it manually. Anyway... I set up the aircraft on a Direct-To route. Once I was steady on course, I updated (resaved) the GFDisplay.ini so the GF46 matched the Shift-Z info readout. I would then shift from GPS NAV hold to HDG hold. and I would change course left or right in 10 degree increments. The GFDisplay never changed. I had it up to 90 degrees off. I then updated the GFDisplay.ini to match things up. I then did 90 degree turns. Here's what I found... When ever the aircraft's bank is less than 15 degrees, the GF46 did not change. Now, there's something to make one say "Hmm!" And this is consistent. If I use Auto-Pilot or manually, the GF46 will not change with less than 15 degrees of bank. (15 is a guess due to the rounding of numbers.) So there's something to throw a wrench in the whole works.

I though as much. I have a dual core, but I wonder what upgrading the affinity will do. I have to run now, but I'll check later. Thanks again, Joe

Wow, didn't expect this coming. Thanks. This is what I'm using in GFdisplay [GF46.0] NEEDS=B E A ; HEADING DISPLAY D0= ="HEAD" D1= X2B00 F64 D302 The reason I'm showing you this is when I'm in the middle of a turn (with high turn rate) the display updates normally. When I'm near the desired course and I start leveling out (with low turn rate), the display stops updating. When I'm steady on course, the displayed heading is up to 7-9 degrees off. If I manually save the GFdisplay.ini, it jumps to the correct heading. At first I thought it was all the other stuff in the ini file so I removed it and had only the Connections and what's above. I got the same result. Any ideas?

I have all my settings to minimum on FSX so I'll investigate my problem there. Thank you for adding the offset to FSUIPC4, I'm positive when I get FSX working right, I'll be using it. And an overall "Thank you" for everything you do regarding Flight Simming. Your impact on this community is unmeasurable. Joe

360/65536 huh? Well, you got me with that. I did take 65535*65535 into consideration for getting the Heading, I just didn't continue thinking. I'm constructing a small generic cockpit. Basically just a small dashboard with some GF units behind it to go under a monitor. Switches & buttons mostly. But I wanted the GF46 right on top of my CH yoke and the rotary knob interferes with the yoke's throttle lever. The GF46 would be behind a thin sheet of plywood and I had hoped to remove the button and rotary. GFConfig initializes the unit to the first instrument setting (Altimeter) and I have to manually select the Gyro instrument. When I realized GFDisplay could set the unit for me, that's when I wrote you about the formatting so I could get the unit placed just right, amongst the other units. I'm not too concerned about gyro drift, I always have that turned off. I suppose I'm not a hard core simmer. I do want a Magnetic Heading, but not one that shifts 15 degrees as I roll. Is FSUIPC4 compatible with FS9? I do have FSX but since I can even get the airport terminals to show up without going below 10fps... I've gone back to FS9 until I get a new machine and haven't even looked at FSUPIC4. If this involves a complete re-write of GFDisplay then never mind, I'll work out another placement scheme.

I'm sorry, you're going to hate me for this... I have two more problems. As the User Guide states, "These two arithmetic operations are the only ones supported, and you can only have one of each". Referring to multiplication and division. In my other post, the "Heading" offset (02CC) is actually the "Whiskey Compass". I didn't realize that until last night, I guess I wasn't paying attention when I found the offset. There is a "Heading" Offset (0580), but it does not take into account MagVar (02A0). The Heading and MagVar offsets require formulas for proper display. So basically I need to add the MagVar to the Heading and have two multiplication & division operations so this can work... D1= X0580 U32 *360 /4294967296 +X02A0 S16 *360 /65536 D302 Is it possible to eventually include this operation and have two of each? Or is it possible some other way to make the calculations? Can you think of another method? Thank you for considering my request. Joe

A kind payment for your service has been sent via paypal. Thanks again!

WHOO HOO!!! You're the greatest!!! Works perfectly!!! I'm so happy you were willing to put forth the time, effort and frustration. You still take donations right?

When I have these problems, I print the section of code I'm having problems with, write down the variables, their types and values passed to them and go outside for a smoke and review it all. This only works of course if the program is fresh in my head. So I know how you feel.

Now that I understand completely, I've had a few old programs so poorly annotated, I had to start over from scratch. Please, take your time. In essence, it is doing what I need it to do, just not what I want Thank you so much for trying. Take care, Joe

Heading now 357.5043 CODE / RESULT D1= X02CC F64 D30 / ___358 D1= X02CC F64 D31 / __357.5 D1= X02CC F64 D32 / _357.50 D1= X02CC F64 D33 / 357.504 D1= X02CC F64 D012 / _357.50 D1= X02CC F64 D101 / ___58_ D1= X02CC F64 D102 / ___8__ D1= X02CC F64 D103 / BLANK D1= X02CC F64 D301 / Overflow D1= X02CC F64 D311 / Overflow ADDED: D1= X02CC F64 D02 / ___357 D1= X02CC F64 D03 / ___357 D1= X02CC F64 D111 / __57.5_ D1= X02CC F64 D011 / __357.5

If I have a three digit whole number and I only specify D1, it still displays three numbers. I was just keeping it clean. I'm not a skilled tester. I should have mentioned, duh, Any double numbers Except D01 (added to previous post, you're too fast for me) produced a blank display (I assume GFdisplay didn't understand and ignored the line) By not specifying the D parameter, I would receive ___242.

First of all, thank you so much for entertaining my ideas. So, The aircraft's actual heading is 241.5688 So that I make sure I understand this formatter: DXifs i = number of numbers displayed BEFORE the decimal f = number of numbers displayed AFTER the decimal s = Number of spaces AFTER displayed decimal numbers with the new version, here is what I get... Code / Result D1= X02CC F64 D0 / ___242 D1= X02CC F64 D1 / __41.6_ D1= X02CC F64 D2 / _1.57__ D1= X02CC F64 D3 / 569___ D1= X02CC F64 D4 / Overflow It seems that the f and s numbers are being combined D1=X02CC F64 D302 / Blank This should have given _242__ Right? Three numbers before the decimal, no numbers after and two spaces. I hope this is enough info. ADDED: D1= X02CC F64 D01 / ____.6_

Hello Mr. Dowson, I'm back with another GFdisplay question and I've read through other posts that you haven't dealt with it in a while, but I'm going to ask anyway :lol: I have a GF-46 under my monitor solely as a heading display and here's what I have programmed into GFDisplay.ini It's working like it should. But, you know me, I have to make things difficult for you. :) The heading shows as a three digit integer aligned to the right side of the display in the last three of the six positions. As shown here ___340 I would like to have the numbers aligned to the left or even better start in the second position. As shown here 340___ or _340__ I've gone through the PDF and don't find any reference to "aligning" numbers. Is this something worth your time adding? I did find one minor issue with the documentation. It's in the Appendix, you have a section Dxxxx: Numerical display format; but not for the Rn display formats. Just thought I'd let you know. Thank you for your time and effort, Joe

Well, hmm. I've been on other hobbies for the past few months. 45=X029C =1; Pitot Heat On 46=X11D0 S16 <0; Temp is Freezing [GFP8.0] L7.1=C45 =1 L7.2=!C45 C46 =1 ffast Here's what I have been using, but my dinner has arrived. I'll check back later to answer any questions.

98=U0,0,K145,8 99=P143,17,Cx0D007B93,x01 That's what you were talking about right? But it doesn't matter, there are so many features and things we can do with FSUIPC, apparently, I have not learned them all. Yet! Thanks for your help, I'm back on track. Joe

Because I've been in the Navy too long. Well, geez! That's just TOO simple!I think this is what threw me off. In that section, you were refering to the FS controls 65536+ and the Additional FSUIPC controls. This is where I failed to make the association. Thank you for bringing me back to the land of "Simple". Have a good weekend! Joe

SHIFT+BACKSPACE is what Mr. Dowson is calling "one shift state". This is one of the functions you want your setup to perform. SHIFT+5 is the other "shift state" he's talking about Don't give up! If you fly for a living, you can figure this out. My conclusion is, if you don't understand what we're talking about, it's just a language barrier. Not referring to the English language, but the programmers/computer geek language. My job for the last three years has been an instructor. If you give up, then don't feel stupid. We failed you. Joe

We can't. It depends on you to know your joystick & nutton numbers. This is going against what Pete tries to do... Duplicating the guides and programming everyone else's stuff. You have to assign a keypress to your shift button so you can find it in the FSUIPC.ini If you assign if to the lower-case letter "a" then your looking for a line like... 123=P1,2,K65,8. 123 is just the line number: this will be different on yours P means to press 1 is the joystick number: this will be different on yours 2 is the button number on joystick 1: this will be different on yours K means Key 65 represents the letter "a" in ASCII 8 means NO shift There is a section of keys and codes you need to make your assignments. You need to figure this out because we don't know your joystick numbers.

Hello Mr. Dowson, SquawkBox3 has the following offset...x7b91 for toggling Transponder Mode from 0=Normal to 1=Standby. It is a 1 byte offset with a decimal parameter. Do I have these FSUIPC.ini lines correct? 95=B7B91=1 P143,17,Cx01007B91,0 96=B7B91=0 P143,17,Cx01007B91,1 According to the log, it's working... 76469 [Buttons] 95=B7B91=1 P143,17,Cx01007B91,x00 76469 .... Offset check: x7B91/1 = 1? (1), Result = TRUE 76469 IPC Offsets Control: Ctrl=x0100, Length=1, Offset=7B91, Param=x0 76469 [Buttons] 96=B7B91=0 P143,17,Cx01007B91,x01 76469 .... Offset check: x7B91/1 = 0? (0), Result = TRUE 76469 IPC Offsets Control: Ctrl=x0100, Length=1, Offset=7B91, Param=x1 But this toggle effect is canceling itself out. How do I get this to effectivly toggle? Also, in the A.U.G. "Format of Button Definitions" you wrote... My suggestion is to specify where this description is.For example: ADDED: ------------------------------------------------------------ I've done some more research. Is this what I need? 95=P143,17,C1005,261 96=CP(F+1,5),143,17,C01007b91,0 97=CP(F-1,5),143,17,C01007b91,0 I'm going to try it and get back here to update my results. ------------------------------------------------------------------- Thanks for your time, Joe

What part are you not understanding? I did a search of the Adv Users guide for "conditional". On the third hit, I found a place where I should lookup "COMPUND BUTTON CONDITIONS". This is on page 19 of 35. Seems to me, what you're looking for is in the first 5 paragraphs.