FSUIPC7 version 7.5.0-beta available for both MSFS2020 and MSFS2024

[John Dowson]

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 0x3304, 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

Latest beta release, 7.5.0b (22nd November): FSUIPC7.exe

Edited yesterday at 02:27 PM by John Dowson
7.5.0b released

[EpixXx]

Amazing thanks, how can i get the WASM folder when msfs 2020 isnt installed on this system? I got a new PC and didnt install it yet. 

Edited Thursday at 05:02 PM by EpixXx

[John Dowson]

1 minute ago, EpixXx said:

how can i get the WASM folder when msfs 2020 isnt installed on this system?

The standalone WASM is available from https://fsuipc.com/

[EpixXx]

Ah got it, thanks 🙂

[John Dowson]

@EpixXx You don't really need anything else from the installer to make it work, but the documentation may be useful, available from the Download Links -> Documentation section of this forum (although may be slightly out-of-date). You will also need the events.txt file (from MobiFligjht) to use the (community) presets - I have attached the latest, just save this to the same folder as the FSUIPC7.exe.

John

events.txt 

[in_04]

@John Dowson thanks for your great work.
I guessed I make everything like you described and FSUIPC starts but crashed after several seconds.

I added all logs and ini files

FSUIPC7.zip

[John Dowson]

7 minutes ago, in_04 said:

I guessed I make everything like you described and FSUIPC starts but crashed after several seconds.

You did not install the WASM. Still, it shouldn't crash - I will look into this. Are you running FSUIPC7 from the same folder as with MSFS2020, or did you copy the folder?
What state was MSFS2024 in when you started FSUIPC7?

Can you install the WASM and try again.

[in_04]

Just started the flight. Before FSUIPC7 is running, stop running as soon as i start the flight. Will install WASM

 

[John Dowson]

19 hours ago, in_04 said:

Just started the flight. Before FSUIPC7 is running, stop running as soon as i start the flight. Will install WASM

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.

Edited yesterday at 02:30 PM by John Dowson
download removed

[jabloomf1230]

Is 7.5a supposed to work the same way in 2024 that it did in 2020?  In 2020, FSUIPC shows up as an option in Settings/Controls for both the throttle an joystick for my Thrustmaster HOTAS Warthog controller. In 2024, even though FSUIPC is running and says that it is connected to the sim, only the default sim assignments show up for the Joystick and Throttle in MSFS 2024 Settings/Controls.

 

[John Dowson]

6 hours ago, jabloomf1230 said:

Is 7.5a supposed to work the same way in 2024 that it did in 2020? 

Yes.

6 hours ago, jabloomf1230 said:

In 2020, FSUIPC shows up as an option in Settings/Controls for both the throttle an joystick for my Thrustmaster HOTAS Warthog controller.

I think you must be mistaken. FSUIPC does not appear anywhere in MSFS2020. What you are probably seeing is a profile (that you created) called FSUIPC.
MSFS2020 (and 2024) automatically creates  profiles for many controllers, but if you assign your controllers in FSUIPC we recommend first creating an empty profile in MSFS.

6 hours ago, jabloomf1230 said:

In 2024, even though FSUIPC is running and says that it is connected to the sim, only the default sim assignments show up for the Joystick and Throttle in MSFS 2024 Settings/Controls.

As with MSFS2020, you should create empty profiles in MSFS2024 for your controllers / devices if assigning in FSUIPC. If you are using the same FSUIPC installation for 2024 as with 2020, then your current assignments should be preserved.

[i3903]

John, I appreciate that you are absolutely up to your eyes at the moment, but I was wondering if you could provide an approximate ETA for the installer?

[kaha]

Will FSUIPC for 2024 then be FSUIPC 8?

 

Karl

[John Dowson]

2 minutes ago, i3903 said:

I was wondering if you could provide an approximate ETA for the installer?

I would like to release this ASAP, by Tuesday or Wednesday next week at the latest.

4 minutes ago, kaha said:

Will FSUIPC for 2024 then be FSUIPC 8?

No - FSUIPC7 is for both MSFS2020 and MSFS2024.

[kaha]

How dose this work? I'm sure I will need different settings for the same aircraft in 2020 and 2024. Also I will need different content in lua scripts. Will there be 2 .ini files and seperate subfolders?

[kaha]

Maybe the events.txt file will also be different between 2020 and 2024.

[John Dowson]

Just now, kaha said:

I'm sure I will need different settings for the same aircraft in 2020 and 2024.

Why are you sure about this? If its the same aircraft, I would have thought the same settings would apply. This is the case with P3D, where I use one installation of FSUIPC6 for both P3Fv5 and P3Dv6 (and sometimes also with P3Dv4).

3 minutes ago, kaha said:

Will there be 2 .ini files and seperate subfolders?

No, just one FSUIPC7.ini file per installation. It is really up to you - you can use the same installation for both MSFS2020 and MSFS2024, or you can have a separate installation for each FS. Personally, I will be using one installation for the time being. If I find any issues with this, I will switch to using separate installations - or see of I need to update FSUIPC7 to handle things differently in some way for each FS.

6 minutes ago, kaha said:

Also I will need different content in lua scripts.

If you need to do different things in lua for MSFS2020 and MSFS2024, then you can just test for this in the script itself, by reading offset 0x3124 or 0x3304,
You could even have one lua script that checks the version, and then starts the lua scripts needed for that version. Its up to you how you want to handle this.
If you prefer separate installations, then just do this.

[John Dowson]

1 minute ago, kaha said:

Maybe the events.txt file will also be different between 2020 and 2024.

And maybe not. If I ever see separate downloads of this file for MSFS2024 and MSFS2020 on the HubHop server, then I will update FSUIPC7 to handle this, and load the specific events.txt file for the FS being used. But I doubt this will happen.

[John Dowson]

37 minutes ago, John Dowson said:

42 minutes ago, kaha said:

Maybe the events.txt file will also be different between 2020 and 2024.

And maybe not. If I ever see separate downloads of this file for MSFS2024 and MSFS2020 on the HubHop server, then I will update FSUIPC7 to handle this, and load the specific events.txt file for the FS being used. But I doubt this will happen.

As you can now access B-vars in calc. code in MSFS2024, there will be some presets that are MSFS2024 specific. There are some discussions on how to handle this over on the MobiFlight Discord server. I will update FSUIPC to handle this once it has been decided what to do. But I wouldn't expect anything to change for some time yet.

[kaha]

Whatever you do is fine, John.

[in_04]

16 hours ago, John Dowson said:

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):

FSUIPC7.exe 676.5 kB · 45 downloads

John

Fix works perfect thanks for fast help 

[John Dowson]

2 hours ago, in_04 said:

Fix works perfect thanks for fast help 

I have updated the version number for this now, available from first post in this topic. A few logging changes also.

John

[LeoSchoonbroodt]

Hi John,
I have a question, if you copy the WASM module from 2020 community to 2024 community, isn't the minimum Game Version in the Manifest way to high, or do i understand this wrong?
I ask because the log tels ne that Lvars are loaded but 0 Hvars while those Hvar file is in the modules folder.
All my Hvars used via lua are not working, while they are working in 2020.

Leo

[John Dowson]

8 minutes ago, LeoSchoonbroodt said:

I have a question, if you copy the WASM module from 2020 community to 2024 community, isn't the minimum Game Version in the Manifest way to high, or do i understand this wrong?

WASM modules compiled for MSFS2020 are treated as such, so I don't think this is an issue. MSFS2024 knows when its using an MSFS2020 WASM.

8 minutes ago, LeoSchoonbroodt said:

I ask because the log tels ne that Lvars are loaded but 0 Hvars while those Hvar file is in the modules folder.

Presume you mean in the MSFS2024 WASM modules folder?
Nothing has changed here - except maybe the aircraft name in MSFS2024. Does your hvar file name match the aircraft name?
Can you activate logging in the WASM and show me the FSUIPC_WASM.log file. Do this with WASM Debug level logging set.

Or maybe you had the hvar files in the persistent storage area for MSFS2020? If so, you will need to copy these to the persistent storage area of the FSUIPC WASM for MSFS2024.

Edited yesterday at 03:46 PM by John Dowson
Further info added

[ljk811]

Hi John, going back to the little flaw I just mentioned.
You probably didn't understand what I meant.
My msfs2024 is the steam version.
I installed the test version of 7.5B in msfs2024. After running MSFS2024, fsuipc will automatically generate the "work" file in this path C:\Users\ljk81\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2020\fsuipc -lvar-module\work

Why is the path of FSUIPC_WASM.log is C:\Users\ljk81\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2020\fsuipc-lvar-module\work\FSUIPC_WASM.log, not C:\Users\ljk81\AppData\ Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\fsuipc-lvar-module\work\FSUIPC_WASM.log

In fact, this is just a problem of programmers' obsessive-compulsive disorder, not a code bug problem.