Обновился FSUIPC4 до версии 4.934

Вчера обновился FSUIPC4 до версии 4.934.
Страница загрузки

FSUIPC 4.934 changes since 4.92

NOTE that this version works with FSX, and Prepar3D versions 1.4, 2.0, 2.1 and 2.2.10438, but no other P3D versions.

1. This version is suitable for Prepar3D version 2.2. build 10438: the one with the hot fix buried in the Prepar3D Forums. It will not work correctly with the original 2.2 release you can download from your account. You must apply the hotfix from Lockheed Martin! Get it from the link in this P3D message. I hope in future that LockheedMartin will put the Hot Fixes in a place where they are more obvious.

2. 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.

3. 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
again]. This new facility is also available in the latestWideClient version (6.999j or later).

4. 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.

5. 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.

6. 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.