The latest beta version of FSUIPC7 is now available with an updated WASM module and a full installer.
Changes are:
- ON ANY RUNWAY simvar has been added to offset 0x0272 as a 1-byte Boolean (read-only)
- AMBIENT IN CLOUD simvar has been added to offset 0x0273 as a 1-byte Boolean (read-only)
- correction to saving state of Open On Start option
- change MF preset name if already exists by prefixing with vendor & aircraft*
- improvements to starting and stopping PMDG-specific threads (used to populate PMDG-specific offsets)
- for MSFS2024, to determine the airfolder, use the folder directly after SimObjects\Airplanes and not the folder containing the aircraft.cfg file
- developer camera state (18) flagged as an in-flight camera state (also in WASM)
- if ini option init3308 is being used, offset 0x3308 will no longer be updated to the correct value once FSUIPC7 is connected to MSFS
- WASM and WAPI both updated to version 1.1.0 - changes are:
- WAPI: allow for sleep/pauses when executing calculator code by adding ' SLEEP::n ' (where n is the number of milliseconds)
into the calculator code string (this will pause the WAPI thread) - WASM: allow for sleep/pauses when executing calculator code by adding ' SLEEP:n ' (where n is the number of milliseconds)
into the calculator code string (this will pause the WASM thread)
Camera state 18 (developer camera) flagged as an in-flight camera state
Only scan for new lvars rather than performing a complete scan for all lvars each time**
- WAPI: allow for sleep/pauses when executing calculator code by adding ' SLEEP::n ' (where n is the number of milliseconds)
- AutoSave menu option only now enabled once FSUIPC7 is connected to MSFS.
* In FSUIPC7, preset names must be unique. However, this is not the case in MobiFlight, and the same preset name can be used in multiple aircraft, As preset names are unique in FSUIPC7, the second and subsequent presets with the same name were previously not loaded and therefore not available. With this change, if a preset name is already taken, then the preset will be renamed to prefix it with the string ‘<Vendor>_<Aircraft>_’, where the<Vendor> and <Aircraft> names are taken from the previous MF comment string that contains these.
Note that if you want details of all renamed and ignored presets, you can set logging for Extras and you will get detailed log messages when the preset files are loaded.
** This drastically reduces the chance of a WASM CTD which has been an ongoing issue for several years now. With this change, the WASM should rarely CTD, although this is still possible.
Asobo have acknowledged that the WASM CTD issue (when calling the gauge API function get_name_of_named_variable) is on their side, and they will work on a fix for MSFS2024 and see if it can be backported to MSFS2020.
This version is available to download here.
John / FSUIPC