Pete Dowson

Do you get reverse throttle using Throttle Decr (i.e. F2 key)? I don't know what John Cook says, but it doesn't matter what throttle axes you use, you just need to assign separate throttles (anywhere, anyway) -- or if you only have one, assign it to the generic throttle and map it to the separate throttles by checking that box in the Calibration tab -- then calibrate just making sure the "No reverse zone" option is not ticked. Pete

I can't make that happen here. I need a bit more info, please. FS version number? FSUIPC version number? (If not 4.948 or later please update first). And maybe a sight of your FSUIPC4.INI file? Pete

Just turn the option off in P3D. It is nothing to do with FSUIPC, those are items of interest only to other add-on developers. L-M were supposed to reverse the option default but they forgot. Pete

Why is 0892 not what you want? It operates the engine start switch. "Start" is the "GND" positon on a Boeing, for instance. Also is it possible with FSUIPC SDK, to simulate constantly pressed push buton, like on keyboard. The SDK provides ways of doing specific things. Buttons by themselves do nothing. You need to say what function you are trying to do. If you want simply to program a button, use button assignments.and simply program the "press" to do one thing and the "release" to do another. Or, if you want it repeating (as it would on the keyboard), select that option instead. Pete

Re-installing tends to make things worse, not better! I need more information. Specifically, the Install FSUIPC4.LOG file, from the Modules folder in your Steam FSX installation. Paste it complete into a message here. Pete

I think you need to post this to a more general forum about simulator cockpits (this one is concerned with FSUIPC and WideFS, two specific software programs), and you need to be much much more specific about what this "simulator" is. The term "simulator" here mostly means either FSX or P3D, to software programs, whereas you are talking about is presumably some hardware? Pete

Have you not tried simply assigning the second to a tiller too? FSUIPc doesn't really care how many axes you assign to each control. The part which operates the gradual changeover tiller <-> rudder doesn't care where the original values come from, only what they are assigned to, and only changing values are used in any case. Provided the tiller not in use doesn't "jitter" it won't interfere. To ensure that make sure it has a central zone defined adequately. Pete

It may be doing a similar thing to PMDG's throttles and taking the controls at a higher level than FSUIPC can feed through calibrated values Try not actually calibrating in FSUIPC, just assigning (press "Reset" on the calibration entries). Alternatively, or as well, ensure you assign to the "axis ..." controls, NOT the plain "aileron_set" and "elevator_set" controls. That, plus no calibration makes FSUIPC assignment identical in every way to assigning in FS execpt you have the Profile facilities too. Pete

Either assign in FSUIPC and calibrate, or wait for L-M to fix P3D (in 3.1 I hope). Pete

You NEVER pay again for FSUIPC3/WideFS6. In fact you are expected to keep it updated or it cannot be supported. Again, you do not purchase "4.948", only FSUIPC4 (and WideFS7). You are expected to use the latest version, whatever that number might be. FSUIPC4 works with WideFS7, not 6. It is the Server which is updated, and in FSX and later the server is incorporated into the FSUIPC4 module for efficiency. But you have to enable it with a purchased registration. 6.995 is actually the version of the Client (WideClient) which works with any version of WideServer and FS. Pete

Sorry, P3D 1.3 was far too buggy for me to support. Why are you "required" to use such an old version? I'm about to drop support for 1.4 too. In fact the only versions worth supporting now are 2.5 and 3.0 (with 3.1 imminent I think). Anyway, the only G3D "fix" which FSUIPC ever implemented was a patch it placed to avoid a crash when data in a BGL file got corrupted in memory. I never had any such crashes myself -- they seemed to occur mostly when the system was running out of process memory. There were many G3D crashes never fixed this way and Terrain ones too. I don't know of any link between them and the use of SimConnect. Pete

As for other reports I see there, It is working fine here. If FSUIPC creates a radar file, then it is connecting okay to ASN, and the file is exactly what ASN is returning. Why that would be affected by a difference in FSUIPC version I don't understand. Maybe it's a question also of loading order in the DLL.XML file. When you install FSUIPC it will be placed at the end. When you install ASN it places its DLL at the end. I think the latter is generally more reliable for ASN which is why it does it. Anyway, I'll need to see the FSUIPC4 log file, not the Prosim logs or the Install log. Also, just in case the minor changes since 4.948 have altered things, could you try this: FSUIPC4948c_TEST.zip Pete

Sorry, I think you must be in the wrong Forum. I don't know any FSX Autosave program. Pete

You must have the same name for both. I can only suggest raising it as a problem ticket with SimMarket. Pete

Execute it! All msi files are installers. Just double click on it! How did you manage to install P3D? That's usually an msi file too. Pete

I assume you mean version 4.948. You can have a different email address for the two, but your name must be the same for both. Pete

It sounds like you have used some sort of migration program to try to install non-P3D programs into P3D. That makes it look like FSX, thus you get problems with real P3D installers like FSUIPC's. If you cannot work out how to undo the damage the migration program has done, show me the Install log file (paste it into a message here) and I'll try to help. Pete

NTDLL just contains a load of standard Windows API functions which really haven't changed at all in many many Windows versions. FSUIPC's use of them is very slight. It is much more likely to be one of the gradually-being discovered glitches in the FS code itself in relation to both Win8 and Win10, mostly in relation to the joystick interfaces. BTW the "Non-scrolling FS msgs to be white" option is merely one bit in a parameter in the message calls to FS, and only apply to messages being displayed at the top of the screen by applications actually using FSUIPC for this. Anyway, glad you managed to overcome it as there's really no way I can diagnose NTDLL crashes. Pete

There's been no change in it I can recall. The code was written once and left as it was. Anyway, I've changed the way I access the bytes as Float (via float * casting instead of direct value casting), so see if this is any better. FSUIPC4948c_TEST.zip Let me know, please. Pete

Good catch! Please ask PMDG 777X support this very good question. Their documentation definitely shows: unsigned char COMM_ReceiverSwitches[3]; // array: 0=capt, 1=F/O, 2=observer values: Bit flags for selector receivers 0...12 (VHFL..APP) as listed above The unsigned char value is 1 byte (8 bits). Pete

That's the LOG file again. I asked to see the INI file, please. Pete

What actually happens, then? Have you tried sing the Lua debug/trace option (in the FSUIPC Logging tab). That should show what is happening. Generally, though, to change the time in FS reliably (keeping the correct difference between UTC and Local Time), I suspect you may need to write the local time, either instead or as well, and maybe also even the difference (offset 0246), even if it isn't changed. Note that any time change which does affect anything other than the seconds will cause the sim to reload scenery texturing and so on, so produce a noticeable stutter. If FS's time is running slightly slower or faster than you PCs clock this will happen regularly. Pete

If the values arriving from the quadrant are changing throughout its movement (and you would see this in the axis assignment or calibration tabs in the "IN" value box), then it sounds simply like you aren't calibrating them properly. You need to follow the numbered steps in the User Guide's calibration chapter. If they aren't changing continuously over the entire range, but only half of it, say, then it is a common Saitek installation error which I think can only be fixed by a Registry edit which has been covered already in the FAQ subforum. Talkng of which, I now see you posted EXACTLY the same message in a new thread in the FAQ subforum. I've deleted it. Please don't put support questions there -- it is for answers to Frequently Asked Questions. However, whilst you were didn't you look for the answer? A few lines above your thread there was the one entitled Some Saitek axes only provide partial movement which surely is closely related to your question? Pete

Ok. I'm still a bit concerned that it might have been related to the new code I added to scan joysticks and assign ID numbers to those which don't have them -- as seems to be the case with the default installs of some drivers for Win8 and Win10. So if it does happen again, please do show me the logs with those added lines in the INI file. Incidentally, I'm away from this afternoon till December 7th in any case. Pete

Er, why are you assuming that? I use FSUIPC to assign buttons for doors! Assigning "progress"? It sounds like you've not even used FSUIPC yet to assign buttons? Just go to the Buttons and Switches tab in FSUIPC Options, then press your button,, and in the dropdown for assignment assign to Toggle Aircraft exit, and in the parameter box enter the door number, 1, 2, 3 or 4. Pete