You are on page 1of 2

FSUIPC 4.938 changes since 4.

NOTE that this version works with FSX, FSX Steam Edition, and
Prepar3D versions 1.4, 2.0, 2.1, 2.2 (only 10438 update), 2.3 and 2.4.


This version is suitable for Prepar3D versions 2.3 and 2.4, and now FSX Steam Edition. Note that certain FSUIPC
actions aren't currently supported in FSX-SE -- these are full wind smoothing (still to be investigated), and the G3D
crash correction (the code is very different there and possibly the bug is fixed?).
The FSUIPC4 Installer copes with both types of FSX-SE installation -- one without a parallel FSX installation, and one
with. Note that FSX is inside your Steam\steamapps\common\FSX folder, and FSUIPC and its documentation resides
in the Modules folder within. This applies to both varieties of installation.


A long-standing bug which can, for some users, crash FSX or P3D during loading, is fixed. Somehow the recent
recompilations for P3D made this bug more prevalent. It was so rare before that it wasn't tracked down.


An additional Lua event library function is available: event.offsetmask. This allows a bit mask to be specified to limit
the events to only changes in the selected bits. For full details please download the latest Lua package from the
Support Forum. [The difference from 4.932 to 4.932a is simply that the value parameter provided to the called function
is that after the mask is applied, so it can be tested directly rather than having to use logic.And to apply the mask
This new facility is also available in the latest WideClient version (6.999j or later).


The Traffic Zapper facility, used as an assignment in FSUIPC or via an offset from an application, crashed P3D 2.x when
used. It seems the function called was identical in every respect excepting that in P3D 2.x it handles only one parater -the earlier versions (P3D 1.x and FSX) took two parameters with the second unused.
The code calling the function has now been fixed.


A problem which may occasionally have caused application display windows to disappear irretrievably is fixed. These
types of Window are used by Lua plug-ins and programs such as Radar Contact.


A serious problem, which caused Lua plug-in threads started by a generic [Auto] section to be murdered as soon as
they were born, is now fixed. Note that this problem would not have occurred when there was also a specific
[Auto.<name>] section for the first loaded aircraft, and it did not affect plug-ins loaded by a RunLua entry in the
ipcReady.lua plug-in.


If a parameter value of -2147483648 (hexadecimal x80000000) is entered when assigning a control to a Key press or
Button, it was displayed subsequently as -0 instead. It didn't mean the value actually used or stored in the INI file was
incorrect, but it was misleading. It appears to be due a bug in one of the Windows dialogue functions being used. In
this version a work-around, using a text function instead of a numeric function, ensures that the display is correct.


A facility to have Profiles separated into one file per profile, to relieve cluttering and large INI files, has been
implemented. For details, please see the separate document about this entitled "Profiles in Separate Files".


Axis polling speed is improved in this version.

10. When used with P3D version 2, FSUIPC discards the .FLT part of any request to load a flight via offsets, so that the new
XML format flight file may be loaded instead.

If the AutoAssignLetters=Yes option is enabled and new devices are added. The values at offset 3F02. When creating a new profile in the Axis assignments tab. 17.0 to 1. 21. An incorrect value for the Lua library mouse. 22. the letters associated for those will remain unusable for new devices.120 times the user-specified value. 13. 19.4 23. This action is logged.e. You should consider deleting unused entries.936b now tidies up the P3Dv2 .dll. existing assignments are now kept for the Profile if this is requested.11. 24. There are only 24 letters available (A-Z less I and O to avoid ambiguity). so it is then possible for the Auto option to run out of letters. Incorrect text shown for the "Aircraft Specific" or "Profile Specific" check box on the Joystick Calibrations tab in FSUIPC Options is corrected.wheel function was being sent to FS -. Similarly the ground vehicles at an airport. Note that this does mean that if you remove devices because they are no longer used or owned. Orphaned [Profile. This is now corrected. 18. Fixed an error which would crash P3D version2 during loading if the text menu intercept option is enabled in the FSUIPC4. those with no assignment or calibration sections in the same file or in the Profiles folder) are now automatically deleted during initialisation so that the Profile can be readded as new. It seems that. . whereby missing devices with names starting with numbers in the range 0-15 could result in substitutions being made in the assignments. Additional checks are added to ensure links to ASN's active check function are valid. The version number of the P3D EXE being used is now available in the one-byte offset 0x3124.INI file. in fact. can find their way into the FSX folder and get loaded even when ASN is not installed. registering when a new flight has been loaded. bad copies of the interface module.0 to 2. Implemented the same comment-saving action in INI file [Keys] section that has long been available in the [Buttons] sections. This allows for a higher density of such vehicles without overload. is fixed. 12.INI file (i.PNL files automatically. The OOMcheck parameter in the FSUIPC4 INI file [General] section can now be set OOMcheck=Quiet to allow the check to take pace (and the offset for VAS maintained) but without sounding the warnings when VAS gets low. 20. An error in the Joystick lettering facility. In error previously these were lost even if you did request they be carried over. somehow. The Autosave option in version 4.4 20 to 24 (at present) for versions 2. which are read for the "DeleteVehicalesForAES" option. 15. The TCAS traffic tables now have a maximum range of 100km instead of the previous 200km This is to allow for much higher traffic levels without causing a deterioration in performance with SimConnect channels being overloaded. is now incremented also in the new flight has the same name as the last one. as_btstrp. 14. are now only read once rather than every second as before.<name>] sections in the FSUIPC4. 16. these are now assigned previously unassigned letters rather than replacing any missing devices with already assigned letters. The values are: 10 to 14 for versions 1.