Pete Dowson

You seem to be misreading it. As it states, it is talking about computing the increment value, the one as displayed in the flaps calibration section of FSUIPC options. The increment value depends on the number of positions. It there are only 2 positions, as you are saying, then the increment is 16383 divided by (2 minus 1) = 16383. Obviously! Because the two positions are 0 and 16383. They have to be! You most certainly are not reading what it says. It is telling you how to compute the number of positions (detentes) from the given increment. The two so-called "formulae" are identical, just inverses of each other. One relates positions to increments, the other increments to positions. As such they tell you how the value in one offset relates to the value in the other. They are, in fact, both derived from the same FS value in the first place by code in FSUIPC using this relationship! Sorry, you've lost me there. if you take full control over the GF-P8 LEDs you can light them or extinguish them as you wish. Offsets showing what? cowl flaps positons are there for each engine -- just search on the word "cowl". And a search on "GPS" will find your NAV/GPS switch in no time. Regards Pete

Sorry, i don't know the device at all. Is it a USB HID device or a USB serial port device? If so you could try using a Lua plug in using the COM library. Might be a quicker development path, or at least a way of prototyping something ready for a C++ program. To get into the protocols of devices I use the tools from AggSoft -- their advanced serial and USB port monitors are very good. You get a trial period with them too, which might even be enough. Regards Pete

They are documented in the Lua documents in your FSUIPC Documents folder. The Clear, Set and Toggle functions work on special flags testable in the Lua program, the Value sets a value (number) for the Lua program to test. The Debug is used by the Lua programmer to help trace through the lines in the program and fix errors, and the Kill, well ... Kills a running Lua program forcibly. I doubt if you'll find any need to use any of those for the types of functions you are looking for. If the aircraft uses the default FS altimeter setting for pressure (the Kollsman window), then the assignable controls are called Kohlsman Inc and Dec. (Microsoft mis-spelled the name Kollsman). If you ever need to see what FS controls are used when you click a switch with the mouse, just enable FSUIPC's event logging and see what it put in the FSUIPC log file. Pete

When you say "disappeared", what exactly do you mean? The current updated version is 4.703. Have you tried that? (Please, always see the Download Links subforum for updates). If you still have a problem, please explain it a little clearer -- I need to know what you actually mean by "FSUIPC had disappeared", as that makes no sense to me. How are you detecting this? Also it would help if you then closed down FSX and retrieved the FSUIPC4.LOG file from the FSX modules folder and pasted its contents into your message. Regards Pete

Er ... the main question is, what aircraft is it you are using, or what external avionics if so, which loses all of its settings rather than includes them in the saved flight files? None of the default aircraft do that -- none save in live flight mode and load back "cold and dark", so it must be a function of whatever you are using instead. Please don't start venturing into areas like FSUIPC offset data saving for no reason (which I think may only apply to FSX in any case. I don't remember offhand -- it's a long time since I used FS9). Tell me why you are losing settings -- as you presumably would if you saved your flights manually and reloaded them. All I'm saying is that all AutoSave does is automatically call the FS save flight routine. That's not really complicated ...? Regards Pete

Following on from your private message: This is a bug caused by some recent Windows updates. Please go to the Download Links subforum and read the update notes there. I think you'll be okay if you use 3.991 instead of 3.99. It is always a good idea to check for updates there before reporting a problem which may be already fixed. All AutoSave does is call on FS to save the flight, exactly as if you saved it via the Menu or using the ";" key. And you reload it as usual. It has nothing to do with anything inside any of the files saved. If you are using complex add-ons with their own systems then they may need to save their own files too and reload them. I think many do, maybe you are using one which doesn't? With Project Magenta systems it depends on FSUIPC offsets, so I use the facilities to always save IPC data (in miscellaneous options) and the Load flight+data menu option. Regards Pete

I've now posted examples and a tutorial for this in the FAQ subforum. Regards Pete

What version of FSUIPC are you using, please? Show me the FSUIPC log. Are you Mr. Haak? If so you appear to have two valid FSUIPC3 registrations, one from 2005 with a different email, and one from February this year with the same email as your WideFS registration. Maybe you have the FSUIPC ones mixed up? If you want to discuss this privately write to me at petedowson@btconnect.com. Pete

I'm starting this topic here to provide permanent links to useful places to go to for more help and information. Please, if you know of others please do add to this thread. To kick things off, here's one website a user pointed me to recently: Flight Simulator Network: FSUIPC How-To Some of the stuff there you can find here too, but it looks useful in any case. Here's a link for Uninstalling and Reinstalling FSX properly. It doesn't seem to consider SimConnect side-by-side library complications, but maybe if you are really carefyul this don't arise: How to uninstall and reinstall FSX, by PMDG Best Regards Pete

Ah, great news! Thank you very much for reporting back on this! Regards Pete

Good! Thanks for confirming this. I can now take the "untested" notice off the changes list! ;-) Pete

Not in any "INI". Save the Lua plug-in from that thread I pointed you too, into the FS modules folder, with a name like "PMDG747.lua", then load up FS, go to FSUIPC button assignments, and assign to "Lua PMDG747" with the parameter needed as listed in that program, or even in the thread itself. Regards Pete

The most complete EFIs controls list I've seen appears in the Lua plug-in given in the User Contributions subforum, in the thread headed "PMDG 747X commands". The lower button row certainly appears there. But to make the selector switches work correctly using increment and decrement only you have to do a little Lua programming I'm afraid. For instance use a parameter value 0-8 to select the range, and to get to position n do 8 decrements and n increments. Once positioned the first time you could save the current position in a global variable and only do the correct number one way or the other, though then you'd need to do a bit of re-syncing if you reloaded a flight.. Regards Pete

The only times ever that FSUIPC's dialogue won't appear in full screen mode is through an inappropriate video driver. It sounds like when you installed your 64-bit Windows 7 you allowed the Windows installer to use its own driver rather than go seek the correct and latest one for your video card. The windows default one is really not good enough. Regards Pete

Sorry, I don't know anything about the Elite stuff. They use their own protocols and own drivers. The PFC relationship is long dead and not relevant anyway as the PFC devices made for Elite were to the latter's protocols, not the PFC ones. Have you tried Elite support? Regards Pete

Ah, right. You should be okay nevertheless, unless they are providing value changes when untouched, which of course is quite possible. Regards Pete

Good. Thanks for letting me know. Pete

Okay. So it's more of a misleading annoyance than an actual problem, now you know? Regards Pete

Okay. Thanks for the feedback. I still can't figure out what was going on on your system, though. Some Registry inconsistency. Let's hope it doesn't return! Regards Pete

Error 2 is simply the Windows error "file not found": you have an error in the path or filename. And remember you need to put it all in quote "..." if there are spaces in it anywhere. Regards Pete

Ouch! I hope you get it back up okay! Regards Pete

GPSout.DLL is for use with FSUIPC3 and FS9 or earlier. For FSX and later the GPSout feature is part of FSUIPC4, and its INI parameters are part of the FSUIPC4.INI file. Regards Pete

I need you to close FS and show me the whole log please. How it ends is as important as how it begins. So far it looks like there's something happening during your system initialisation process which is reverting parts of the Registry to an older copy. This is a complete new occurrence -- I believe no one else has had such a problem in the 12 year history of FSUIPC! [LATER] Can you try 3.991, from the Download Links subforum, and see if the changes I've made to the registration checking help. Let me know, please. Regards Pete

Which FS controls? Increase Autobrake Control and Decrease Autobrake Control? If they've changed their code to ignore the FS setting and only do their own method it won't please a lot of cockpit hardware owners that's for sure. Seems an odd thing to do for a company which seems to be very well oriented towards enthusiast needs. Have you asked them about it? Well, unless you can get iFly to implement something which responds to a value (0-5) to set the desired position I'm afraid all you can really do is assign one of the A/B switch positions to Increment and the another to Decrement, with an unassigned one between. Say RTO = decrement, 1=increment. Leave the switch on Off normally, turn it to 1 and back to increment, or RTO and back to decrement. A bit naff, but otherwise the only solution would be to use a Lua plug-in program to process the FS value (0-5) and send the appropriate numbers of incs or decs to the aircraft. I believe it would be worth asking iFly about this. It shouldn't be hard for them to implement a suitable control internally. Regards Pete