Pete Dowson

All this most certainly sounds like faulty driver installations. The delays and omissions are because the enquiries made through the Windows API to ascertain what devices exist, and to get information about them, is causing hangs in those lower levels. I suggest you go to the Windows device manager and tell it to remove all serial port devices, then re-boot and get them freshly installed, hopefully with updated and working drivers. If the problem is down to corruption in your registry this may also help to clear that. Regards Pete

When you used the information in PMDG's ".h" file to work out the number for the control you want to use, you assign it to watever keypress from your GamePad you want to use, within the drop-down list in the jey assignments tab in FSUIPC. You'll see the item at the top of the list, it is entitled "<custom control>". select that and enter the control number. If you are still confused I suggest you ask over in the PMDG support foruum. I don't use the PMDG aircraft myself. I can answer questions about FSUIPC but not a lot about PMDG add-ons. Pete

You don't need to edit it, just refer to it. The many controls are listed at the end of that file. Pete

and you said Regards Pete

Whether you assign controls to keys or to buttons makes no different to what actual controls you have at your disposal. The PMDG 737NGX is rather different from default FSX aircraft and has its own controls for almost every aspect of its operation. You can assign keys to the special control numbers used in the PMDG 737NGX. You need to refer to the ".h" file provided in the PMDG 737NGX SDK for the appropriate control numbers. And you need to use a recent version of FSUIPC -- version 4.86 is now the earliest supported and was released today. Regards Pete

Oh, right. Well if it renames the P3D exe then all the files FSUIPC needs have to be renamed too. I think I see what the OP was getting at now -- he adapted the INI file name but probably forgot to also attend to his KEY filename, which would have made it appear unregistered. Thanks, Pete

They are actually a form of short cut or 'cheat', performaing the several distinct actions really required, including moving the idle/cutoff lever to 'idle' if it isn't already there. If you ever want to stop the engines you will still need to configure a button to move the lever to cut-off. Regards Pete

Do you mean the Start switches in the overhead of the default FSX 737? The ones which only provide "GND" and "FLT", not the correct "GND-OFF-CONT-FLT"? I think they aree just dummies, not having any useful function. Are, you mean the fuel cutoff/idle levers on the facing side of the throttle quadrant. All FS jets (since the early days of FS) have the fuel cutoff/idle controlled by the MIXTURE controls. The control to cutoff is MixtureN lean, and to move it to idle, for starting, it is MixtureN rich, where N is the Engine number. Surely you've used these to start or stop jet engines in FS before now -- eg via Ctr+Shift+F1 or F4? Those send the all-engine versions of those controls. Regards Pete

If it is seen by Windows as a keyboard, it will be seen by everything, including FSUIPC as a keyboard. Program it in the Key assignment tab of FSUIPC. Regards Pete

Hmm. Strange. One thing I do notice is that, although you are assigning in FSUIPC, you are assigning to the normal FSX controls, which apart from the ability to auto-switch assignments for different aircraft/profiles, is effectively the same as assigning in FSX instead. FSUIPC calibration is independent of where you assign (or it should be), but FSUIPC's most efficient form of assignment is "direct to calibration" as that saves a few steps which otherwise the controls have to go through. Anyway, back to the point. I've tested your INI settings here with my very latest version and everything seems okay, so could you please just try the new release, 4.86? It isn't quite there yet -- I'm just finishing some documentation updates -- but it will be available within the hour. Thank you, Pete

What's "legacy mode"? Please run P3D normally. Regards Pete

No, if they are loaded they are running. visibility isn't relevant. Regards Pete

You do realise these are accelerations, not the actual current pitch, roll and yaw values? Also they are 64-bit ("double") floating point numbers, not integers. You are only reading the least significant 32-bits as if they are integers, which will give you rubbish. Please do actually read the details provided in the Offsets list which tell you all this. Accelerations are NEVER "in degrees", degrees per second per second maybe. Velocities are in radians or degrees per second, only the actual angles can be measured in degrees. Pete

Sorry, I thought I'd replied about two weeks ago, but I don't see it here. Odd. I did some research on this and all I could find is ways of making a GPS gauge. It's a completely different sort of programming and it would be a completely separate module -- ideally a GAU file as that makes it easier to program by the look of it. Probably best written in XML. You could probably adapt an XML-written GPS module to copy all the values you want into L-Vars, then they would be accessible in Lua as it is. I'm afraid none of this area of programming is something I've any experience with, and I really don't have the time nor motivation these days for learning something so new. Sorry. Regards Pete

The R and Z axes are NOT the same, and nothing will read one as the other. It sounds like you have a Z axis which it jittering. Just use the "ignore" button to temporaily cause the assignments tab to ignore Z. But also be sure that this "R" axis is really your rudder. This is not usually the case. "R" doesn't mean "Rudder". The usual axis names are X Y Z U V R. Sliders are usually P and Q but the others can be anything. Pete

There's been no change in any of this part of FSUIPC. I suspect you have something else going on there. If you want more help on this I would need to see your FSUIPC4.INI file, which you could paste in a message here. Also you could try enabling Axis logging in the Logging tab to see what is happening yourself. Regards Pete

The AI traffic tables only contain data for AI traffic. There is no "state" information for your own aircraft, only its position, speed, altitude, etc. YOU, the pilot, are supposed to know whether you are departing or landing or taxiniing or whatever. How could you not know? If you want a program to tell you what you are doing it would be a matter of guessing from the various values describng the aircraft's current actions, like whether you are moving, whether you are on the ground, whether you are descending or climbing, and so on. But honestly I don't see the point? For AI Traffic they read it from FSUIPC or direct from SimConnect. For the user aircraft they take note of what you are doing. The can't actually know you are 'boarding'. That's just a guess based on the fact that you are parked with the doors open. Taxiing is just moving at slow speeds on the ground, or even stopped but not at a gate. Taking off is moving faster on a runway. Departing is climbing away from the airport. Et cetera. Regards Pete

There appears to be no question in your post. However: Offset E080 is the start of a 96 item array of structures, each one of which may or may not contain current details of an AI aircraft on the Ground. Just getting the flight status of the first entry may or may not tell you anything, depending on whether the slot is used or not. And having the status of one odd AI traffic aircraft on the ground seems a little pointless? I don't know VB.Net, but is a "BitArray" literally an array of bits? If so, getting the 38th bit isn't related to the structure at all. The offsets withing each of the 96 structures in in bytes -- byte 37 in each of the 96 entries will contain the status of that particular aircraft if, indeed, that slot is actually in use at that time. Also, doesn't VB count from 1? In other words, isn't [37] a reference to the 37th entry, not, if it were bytes, the byte at offset 37 from the start (the first being 0)? Finally, I have some recollect than the VB expression "&HE080 will actually give the hex value FFFFE080, which you certainly do not want. I think you have to postpend another & to stop the sign extension -- but please check in your VB manual first as I'm not 100% on that. Pete

There isn't one, that's why. It isn't something supplied by FS You'd have to compute it by reading the latitudes and longitudes and doing the trig at regular intervals. Pete

You misunderstand the purpose of the INI file. It is the place where you are settings are stored, not a text file for casual perusing. Please use the options dialogues, as intended. If you want to mess in more detail, then you need to do the cross referencing yourself. The INI file is a standard configuration profile maintained by standard Windows APIs. Its format is not mine to decide. Regards, Pete

Thanks. Perhaps you could re-post to the User Contributions subforum, with a suitable title. Then it won't get lost. Best Regards Pete

Did you close the Options menu with OK before looking at the INI file? Assignments are not saved until confirmed in this way. Why were you looking in the INI file in any case? What do you mean by "A10, A11 etc"? Do you mean joystick A, button 10, 11, and so on? You are using Joystick Letters? Please always state the Version of FS (it is quite important) and the Version number of FSUIPC. If you are not using a supported version (at least 3.999w or 4.953, at present), please update first. Regards Pete

Not hostile, just don't understand why you don't read what it says. Those two entries in the offsets lists have not been changed in years, having been correct all that time. And I don't understand how you can misunderstand them. As I said, you are even told how to convert to fpm. Sorry, you'll need to ask Paul about that document. In my document all numerical values are integers unless otherwise stated as Doubles (64-bit floating point), or Floats (32-bit floating point). However, the units may indicate that they are effectively fixed point rational numbers in integer format, hence the conversions. Pete

You entitled this thread "GPS Altitude not working", yet I see no further reference to this. Why is that? I have no idea what you mean by "Single" (is this a term applicable to whichever .NET language you are using?), but as a programmer you must know that a 4 byte value contains 32-bits (4 x 8 ), which is the standard integer size in a 32-bit process (as of course both FS9 and FSX are). You therefore need to use whatever variable type a 32-bit integer is in the language you've chosen. Are you converting it properly into FPM? Sounds like you are not! If you refer to the offset documentation again, you will see that this offset is only a COPY of the proper V/S at 02C8. Unless you are only wanting touchdown speed (which is what this is for) you should be using 02C8. If you bothered to refer to 02C8 you will see it clearly says that the units are in 256ths of a metre/sec. It even tells you how to convert it!!! Pete

I just did a search in this Forum for "Reversers" (didn't you try that at all?), and found: using-fsuipc-with-pmdg-738ngx-throttle-help-needed fsuipc-throttle-assignments auto-throttle Maybe there are good ideas in those? Regards Pete