John Dowson

BTW, what version of FSUIPC5 are you using? The latest (supported) version is 5.15.

Maybe you should take a look at Paul Henty's client dll for .net - I haven't checked myself but I think thats more OO and may have callback facilities....of course, c# not c++. Cheers, John

Hi Skip, strange that this has returned...I'll look into this and get back to you. Cheers, John

Yes! You could, of course, write a wrapper around the provided functions to implement a callback mechanism if required... 4.974 is the latest supported version, however there is a version 4.974b which contains an improved Lua ext library (see the 'Updated Modules' support page: ). Cheers, John

Also, please see this thread (originally for FSLabs A320) for a general discussion on steering using the tiller/steering axis rather than rudder:

Hi Morten, what did you see this? Its fine to send one axis to "send direct to FSUIPC Calibration" and another to "FS as normal axis". Of course, each axis itself can only have one destination. Can you also check that you have the controllers in P3D disabled (maybe they became active again after your P3D update?). There is no “front wheel” control used in FSUIPC. You may be able to use the FS control “STEERING SET” which I think was new to one of the releases of P3D and so never used by FSUIPC in its controls. Steering on the ground has always been by rudder operation, hence the blending between the steering tiller operation and the rudder. “Sharp turns” in a PMDG 777, or really any airliner, need low speeds, and judicious use of differential braking and, yes, occasionally asymmetric thrust (as the aircraft slows even more during the turn). I don't fly PMDG aircraft, but maybe some other PMDG users could help you out here. I'm actually surprised that using “send direct to FSUIPC calibration” on any PMDG Boeing airliner works at all. Those tend to read the control values themselves direct from Simconnect, whilst FSUIPC is calibrating them and sending (possibly different) values at a much lower Simconnect priority level (to avoid an infinite loop). This generally give unwanted jerkiness. Cheers, John

Hi, is this still an issue? you have the same Joy id number (2) assigned to both your wheel and throttle, but I guess you already know this. What do you mean by ' I have tried using the JoyIDs but without help'? What is your issue with JoyIDs? You can also try editing your INI file to assign a new Joy ID number, as explained in this (and other) post: Cheers, John

Hi, you posted in the FAQ section - I've moved your post to the correct location (FSUIPC Support Pete Dowson Modules). You can just re-run the installer to re-install and re-register your product using the registration details from SimMarket. You will, of course, have to re-assign/reconfigure everything again unless you saved a copy of your ini file. Cheers, John

Hi Robert, As Chakko says, the ambient pressure doesn't change very quickly, which is why you are seeing slow updates. If you monitor offset 28C8 and go into slew mode and slew up very fast, I see the following logged: 1115813 Monitor IPC:28C8 (FLT64) = 2071.1340 1115813 SimRead: 28C8="AMBIENT PRESSURE" [also 28E8] FLT64: 2071.13404498 1115891 Monitor IPC:28C8 (FLT64) = 2070.8867 1115891 SimRead: 28C8="AMBIENT PRESSURE" [also 28E8] FLT64: 2070.8867444 1115985 Monitor IPC:28C8 (FLT64) = 2070.6393 1115985 SimRead: 28C8="AMBIENT PRESSURE" [also 28E8] FLT64: 2070.63931635 1116078 Monitor IPC:28C8 (FLT64) = 2070.3920 1116078 SimRead: 28C8="AMBIENT PRESSURE" [also 28E8] FLT64: 2070.39201578 1116125 Monitor IPC:28C8 (FLT64) = 2070.1446 1116125 SimRead: 28C8="AMBIENT PRESSURE" [also 28E8] FLT64: 2070.14458772 1116219 Monitor IPC:28C8 (FLT64) = 2069.8974 1116219 SimRead: 28C8="AMBIENT PRESSURE" [also 28E8] FLT64: 2069.89741462 1116297 Monitor IPC:28C8 (FLT64) = 2069.6500 1116297 SimRead: 28C8="AMBIENT PRESSURE" [also 28E8] FLT64: 2069.64998657 The interval here varies between 80-100ms. Note that there is a delta value set on 28C8 (i.e. changes less than this are not reported) of 0.00009F, which should be fine. With further tests, also monitoring/logging 3498 (ambient pressure in millibars) and the altitude (6020), it looks like the sim is only updating on millibar increments above 0.12-0.16 or so (or about a metre). Interestingly, slewing down slowly (Z) seems to go at a rate of about a meter per second, logging the ambient pressure roughly once per second, while slewing up slowly (F3) seems to go at about 15m per second, logging the pressure around 12-15 times per second. In summary, I think the rate is down to SimConnect rather than anything in FSUIPC5. Cheers, John

Hi, such issues are usually caused by usb power management/sleep issues. Check the power management on your USB hubs and make sure the setting to allow the computer to turn off the device when not being used is disabled. Cheers, John

Hi Roman, I'm still quite new to lua myself, so I'll leave it to Pete to answer your questions when he returns. However, thought I'd mention that you can always use the 'event.button' (set of) functions instead to call the function on the button press without going through the FSUIPC assignment to toggle/set a flag. Cheers, John

It will be added to the next release. Cheers, John

Hi, Pete's still away, but I took a look and could reproduce and it seemed to be an easy enough fix, so please try the following: FSUIPC5150b.zip I'm not too familiar with this flag/functionality, so I'll get Pete to verify when he's back. Cheers.

You don't need to uninstall - just download and run the 5.15 installer. If you have already registered you can skip that step ('Not Now') and your existing key file will be used (and checked when you start P3D). You can dowload from here: Cheers, John

I could populate 0628 for read access based upon the values in 3402 if this would help?

Hi Tom, where does it say that it is a 'Beta copy'? There is no such thing! Version 5.121a is an interim version and is out-of-date (not supported) - please download and install version 5.15, which is the latest version of FSUIPC5. There are only registered and unregistered versions (and no expire date!). The 'About' tab in the FSUIPC5 main window will show if the copy is registered or not, and the FSUIPC5.log file will log the registration check (when you start P3D). What does this say? Cheers, John P.S. For future reference, could you please use a more useful topic....'FSUIPC' doesn't say much, 'FSUIPC registration query' would have been better! Thanks.

Hi Luke, I can confirm that 0628 does indeed remain zero. However, looking at the offsets document, this is defined as 'No' for both read and write, i.e. Not Supported. I guess it could be added, but I am not sure this is worth doing anymore now that offset 3402 contains the more detailed mode info. Cheers, John

WideClient is available from the 'Download Links'->'Updated Modules' page:

Hi Luke, I'll take a look at offset 0628, but I think you are better off switching to use 3402. You cannot disable the use of the PDK now, since version 5.14 (see note 18 of the 5.14 release note). Regards, John

The 'Miscellaneous' tab is one of the tabs in the FSUIPC main window. Are you using FSUIPC, or is this a general P3D question? This is the FSUIPC support forum. If your question is about P3D then best to post in their forums. Regards, John

Hi Don, you can connect your USB devices to your client computer and connect using WideFS. This will generally be fine for buttons/switches/toggles, etc, but for axis controls (throttle, elevators, ailerons, rudder, etc) you may find the added delay (due to the network) gives poor response times. Anyway, Pete will be back next week so please wait for his opinion before you splash the cash! Regards, John

Hi Luke, there were some changes in the way the sim mode is derived that were introduced in FSUIPC v5.15. See note 5 in the 5.15 history document. There were also some changes in the use of offset 3365 (which is the 'in-menu' or 'dialog' flag) in v5.14 (please also see History document for details) The sim mode is now taken from the PDK and stored in offset 3402 as a bitwise flag. Please check the offset status document for this offset. There is no change in offset 0628 - this should still be 1 when in instant replay mode and 0 when off. Cheers, John

Hi, if your original problem is fixed and this is a new problem, could you post a new topic please? Please also post your FSUIPC5.ini file for assignment issues. Are you using profiles? As mouse-macros are aircraft specific, they should really only be assigned to a profile. Cheers, John

Hi, unfortunately it is difficult to tell what is in the attached image, but yes - the 'Previous Flight' should be visible in the 'Load Scenario' dialog box. I am not sure why the 'Previous Flight' is not visible, if it is there and visible in the 'Save Flight' dialog box, it should also be in the 'Load Flight' one.... You could try activating the 'Provide menu entry for flight loading' option, in FSUIPC's 'Miscellaneous' tab. This will give you an extra 'Load Flight...' menu option in the 'Add-ons' drop-down. Use this to navigate to your saved flights directory (usually in the Documents/Prepar3D v4 Files directory of the user account - this should be the default) and see if you have the 'Previous Flight.fxml' file there and try and load that. Cheers, John

Hi Maksim, could you please also post your FSUIPC5.ini and FSUIPC5.JoyScan.csv files please, both also located in your Modules folder. Thanks, John