Leaderboard

Download removed - please now download updated installer - see Please find attached below the latest FSUIPC7 beta release, which has been updated for MSFS2024. You should use this release for both MSFS2020 and MSFS2024. To use this version, please make sure that you have first updated to the latest FSUIPC7 release, v7.4.18. If not using that version, please download and install that first. Then rename the current FSUIPC7.exe (e.g. to FSUIPC7.exe.7418) and then download the attached FSUIPC7.exe and move/copy that to your FSUIPC7 installation folder. It is also a good idea to make a back-up of your FSUIPC7.ini file. and also the Profiles folder if using profiles-in-separate-files. You can either use the same FSUIPC7 installation for both MSFS2020 and MSFS2024, or you can have separate installations for each. If you prefer the latter, please copy/paste your current installation folder to create a new installation for MSFS2024. I will be updating the installer for MSFS2024, but for the time being you will have to either install manually for MSFS2024 or manually start FSUIPC7 once MSFS2024 is running. It is recommended to manually install the FSUIPC WASM module into MSFS2024. To do this, simply copy the FSUIPC WASM module folder (called fsuipc-lvar-module) from your MSFS2020 Community folder to your MSFS2024 Community folder. If you do not know where your Community folder is located, check the value of the InstalledPackagesPath variable defined on the last line of your UserCfg.opt file, which is located For Steam installations, under %APPDATA%\Roaming\Microsoft Flight Simulator 2024\ For MS Store installations, under %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\ If you would like FSUIPC7 to be auto-started with MSFS2024, you need to add an entry to the EXE.xml file, if it exists, or create this file and add an entry for FSUIPC7. The location of this file is the same folder as the UserCfg.opt file, shown above. The contents of this file (to start FSUIPC7 only) is as follows (please check and update the Path to point to your installation): <?xml version="1.0" encoding="windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>EXE.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Name>FSUIPC7</Name> <Path>D:\FSUIPC7\FSUIPC7.exe</Path> <CommandLine>-auto</CommandLine> <NewConsole>False</NewConsole> </Launch.Addon> </SimBase.Document> The changes in this version are: - added ability to adjust event priority levels. This can help some add-ons work correctly, and make more events visible to FSUIPC7. However, it is only recommended to adjust these when directed to by either support or aircraft providers. - automatic adjustment of priority levels for FSLabs A321 aircraft - re-factored building of the FS Events table with the following new events added: CAPTURE_SCREENSHOT, DECREASE_DECISION_ALTITUDE_MSL, INCREASE_DECISION_ALTITUDE_MSL, LETTERBOX, MOUSE_LOOK_TOGGLE, MP_PAUSE_SESSION, VIEW_TYPE - forced uniqueness of preset names. Presets with duplicate names will no longer be loaded. - Removed EventsViaCommands ini parameter, as this is not applicable to MSFS2020 or MSFS2024 - corrections to pause state for MSFS2024 - update offsets holding Input Events directly when writing to them. This seems to be necessary as Input Events sent from FSUIPC are not being received back (as they are in MSFS2020). I will report this to Asobo. - logging of received Input Events corrected. Previously received Input Events weren't logged unless the DontLogTheseIE ini parameter was set - For MSFS 2024, write the value 14 to offset 0x3308, and the value 120 to offset 0x3124 - folders used for saved flights and plans updated to use MSFS2024 folders (when using this version) - separate AutoSave sections now used for MSFS2020 and MSFS2024 Please use this topic for any issues/feedback with this version for both MSFS2020 and MSFS2024. I will continue testing this version, and will look into updating the FSUIPC7 installer to be able to install into both MSFS2020 and MSFS2024. John

Yes, very strange... I will be releasing 7.5.1 later today, and I am going to switch to using version numbers on the downloadable file which should help with this cache issue. Cheers, John

This is an MSFS issue and nothing to do with FSUIPC. You should use the MSFS/Asobo forums for this issue, not this FSUIPC forum. Sorry, but I can only help with FSUIPC issues, not MSFS issues. I will leave this post in case anyone else has any suggestions, but you are better off using the Asobo forums for such issues. I have also moved your post to the FSUIPC7 / MSFS forum as you posted in the main support forum. John

You should use FSUIPC's logging facilities to work out what is happening. Set logging for Buttons & keys, open the logging console and see what is logged when you press the buttons - this should tell you what is happening. But if button 0 is already pressed when you press button 1, line 34 will NOT be triggered as that assignment is on button 0. Assignments are only triggered when the main/assigned button is pressed/released, not when the compound condition is changed. So, assignment 34 should be on button 1 with the compound condition on button 0 being pressed, i.e. 34=CR(+0,0)0,1,K190,8 -{Key press: .>key}-

And for me the exported Profiles/Actions look the same as in your Setup - Nice! I think that is the Way going forward - even old (pre 0.8.0) Profiles imported stay pretty much the same now 😀 Thanks for your Help 👍

There is no point adding that line again if its already there, and that is to dix a specific problem - to fix issues with 3rd-party programs that are expecting a value in that offset even when FSUIPC is not connected to the FS (i.e. basically for software not yet updated for MSFS2024). If you get any issues with a new release, you should always raise a new support topic. John

Sorry but can you please five your topics a more appropriate title... I will update it... 7.4.18 attached below - save and remove the .7418 extension... John FSUIPC7.exe.7418

Would have been helpful, can't replicate that: - Created a Simple Button Action (Control, 65798, no Toggle) on 0.7.12 - Installed 0.8.4 - Checked Action: Toggle still disabled So for the Moment I can just assume you had actually set a Toggle Switch unintentionally. And that a Setup of Toggle Switch enabled +no Alternate Command+ no Monitor Address + no Monitor Value/Comparison just behaved differently with a on pre-0.8.0 Versions 🤔

Hi John - thanks for the update and appreciate you spending the time looking at this.

FSUIPC7c installs perfectly in MSFS2024, MS Store version as a separate installation. FSUIPC now is started by 2024. Testing is for me limited because the planes I most use are not yet validated for 2024. I tested the ATR42/72 and the C172 with the .ini file copied from 2020 and so far so good. Also my Electronic Flight Bag (EFB2) can be connected to 2024 and I see my plane and the by Beyond ATC injected AI traffic on the map. Thanks! Hans K

Not at the moment - you would have to use separate installations, or ini files. Maybe. I can kook into this after 7.5.0 has been released.

Hi John, apologies for the delayed response, been on my holidays (was lucky enough to sit in a real A321 front seat due to a delay), however by adjusting the affinity mask that seems to have resolved it, it does seem that delay was the issue.. I can't help but wonder if somewhere in the latest updates to the fenix some additional load has been added as you noted. I'll keep an eye on the situation but I think that seems to have gone along way thanks again James

You are a freaking genius! Worked like a charm. Thanks again for your assistance and Happy Thanksgiving!

Strange question...depends on the device, but generally yes (for HID joystick type devices - other devices may need additional drivers or lua), in a licensed/registered version. Device / controller handling in FSUIPC7 is exactly the same in MSFS2024 as for MSFS2020.

I am considering this for the next release.... John

Hi Paul, My app is for airline pilots so I am aways using complex aircraft at complex airports. MSFS2024 is still rather flakey so I think I will hold off on further testing until things stabilize more. Thanks for your assistance. Rob

You have lvarScanFrequency set to -10, i.e scan every 10 seconds. To prevent the WASM crash, you need to disable lvar scanning by setting this to 0, and maybe also increase the lvarScanDelay parameter - but not necessary if any lvars that you are using directly (i.e. not via presets or calc. code) are found in the first scan, You only need to increase this is using lvars directly (adding to offsets, or in lua or macros) and they are not found in the initial scan. Please see the FAQ entry on this issue.

Presume you mean 7.4.18, no? If not, please update. If using 7.4.18, please check the first line of your FSUIPC7.log file. If it has a build date of 1st November, i.e.: then please download and re-install. it should say 3rd November: The initial release was accidentally built using the SDK from MSFS2024, and I corrected this the following day, If that is not the issue, please show me / attach your FSUIPC7.log file. Ah...just seen your updates... Yes, that is definitely the issue - please update. John

I would like to release this ASAP, by Tuesday or Wednesday next week at the latest. No - FSUIPC7 is for both MSFS2020 and MSFS2024.

Found the issue - was missing a check if the wasm was available before checking if it was active. Corrected in the attached (no version number update or build date update with this one): John UPDATE: download has been removed. The latest version available from first post in this topic.