FSUIPC7 version 7.5.0-beta available for both MSFS2020 and MSFS2024

[LeoSchoonbroodt]

Yes copied the complete fsuipc-lvar-module folder structure from MSFS2020 community to the MSFS2024 community.
It's an aircraft copied from the MSFS2020 community folder and the name isn't changed. 
Also confirmed because the plane loads and corresponding profile file and lua file are loaded.
I will check the persistent storage locations and let you know if that's the case and will enable WASM debugging

BTW also ipc.execCalcCode wich i also use a lot for sending Hvars because you stated earlier that it not needs to know the Hvars did not work.

Leo

[LeoSchoonbroodt]

John
Totally forgot were this persistant storage is, i have done it before but it's totally gone now from my memory, can you point me to it?
I cant find ant FSUIPC in AppData\Local but also not in Roaming were all the other apps store their data.

Leo

 

[SMN204]

MSFS 2024
Piper PA-24-250 Comanche.

Followed your instructions for the 2024
 - Replacing FSUIPC7.exe ( v7.4.18 to v 7.5.0 beta)
 - fsuipc-lvar-module from MSFS2020 Community folder to MSFS2024 Community folder

Starting FSUIPC manually after starting MSFS 2024 before flight start
Start flight
FSUIPC works fine at first, but stops working after a few switches.
Rebooting FSUIPC does not help!
Only exit from MSFS 2024 and a new start.
After restart MSFS2024 everything happens again

P.S
Noticed that only what is assigned on the right side stops working.


The one on the left continues to work!

 

 

FSUIPC7.log

[kr283]

HI John,

I'm seeing an issue with FSUIPC7 hanging when trying to List LVARS through the Add-ons -> WASM -> List Lvars

FSUIPC7.log doesn't appear to show any errors, but can attach if needed.

 

Thanks

[LeoSchoonbroodt]

Hi John,
From the FSUIPC_WASM.log i can see that it doesn't find the .hvar file for the plane. although they are present in the fsuipc-lvar-module\modules folder of 2020 and 2024.
They are NOT listed in the layout.json, but for 2020 that was never a problem.

In the persistent storage i find a MSFS2020 and a MSFS2024 folder.
Only the MSFS2020 folder contains a  the fsuipc-lvar-module folder with only a work folder, containing the attached FSUIPC_WASM.log but no modules folder with hvar files.

Is it possible that FSUIPC only looks for hvar files listed in layout.json as that would explain why the 2 not listed therein are not found?

Sorry forgot to mention:
several calculatorcode executions worked this time but stopped after a few seconds.

Leo

[jabloomf1230]

9 hours ago, John Dowson said:

Yes.

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.

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.

That's the first thing that I did. I duplicated and cleared the throttle and joystick presets, renamed them and made them default. The axes from the FSUIPC ini file were picked up, but the buttons were not. In any case, MSFS2024 continued to used its own presets for the buttons, so maybe the clear function in the controls settings doesn't work. Here's the log file, but whatever's wrong is something to do with my setup and I'll keep trying to figure it out.

FSUIPC7.log

[John Dowson]

1 hour ago, ljk811 said:

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

Because that is the folder MSFS2024 has designated for this WASM. Presumably because MSFS2024 detects that the WASM has been compiled against the MSFS2020 SDK.
I wouldn't worry about this - I certainly aren't!

1 hour ago, ljk811 said:

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

Then please try and restrain this instinct...at the moment its difficult to get anything done when I am continually answering support questions....

 

[John Dowson]

@LeoSchoonbroodt Are you actually using the hvar files? These are only needed if using in lua or macro scripts (or via offsets). It is far easier to use presets, where these files are not needed., I am going to remove these as they are continually causing issues and are really not needed anymore. They are a hangover from the early days of MSFS2020.
If using hvars directly, switch to using presets instead. If using presets for hvars, stop going on about hvars and just talk about presets.

1 hour ago, LeoSchoonbroodt said:

In the persistent storage i find a MSFS2020 and a MSFS2024 folder.
Only the MSFS2020 folder contains a  the fsuipc-lvar-module folder with only a work folder, containing the attached FSUIPC_WASM.log but no modules folder with hvar files.

 Of course not. They are only there if you add them. I do install some hvar files, but they are installed with the FSUIPC WASM folder under your Community folder. As with the FSUIPC_WASM.ini, there is an order to how these are loaded, but please see the Advanced User guide - I am not going to explain this again when this has nothing to do with MSFS2024...
It all works in exactly the same way with MSFS2024 as with MSFS2020, only the locations have changed. I will update the documentation with the new locations for MSFS2024 before I release officially.

@SMN204  Looks like you are suffering from a WASM crash. See the FAQ entry on how to resolve this - but take care to use the MSFS2024 locations. If you had this in MSFS2020, you probably added an FSUIPC_WASM.ini with updated ini parameters to resolve  this in your MSFS2020 WASM persistence storage area. You need to copy this across to the MSFS2024 WASM persistence storage area.

@kr283 Your issue also sounds like a WASM crash (IF you have the WASM installed). Please check the FAQ entry on what to do. But it is A:WAYS helpful if you can attach a log if/when you have issues. If I need further info or additional logging, I will ask. But attaching a log when you experience am issue is always helpful, and I would encourage everyone to do this - it can save a lot of time...

52 minutes ago, jabloomf1230 said:

That's the first thing that I did. I duplicated and cleared the throttle and joystick presets, renamed them and made them default. The axes from the FSUIPC ini file were picked up, but the buttons were not. In any case, MSFS2024 continued to used its own presets for the buttons, so maybe the clear function in the controls settings doesn't work. Here's the log file, but whatever's wrong is something to do with my setup and I'll keep trying to figure it out.

@jabloomf1230 The clear function in FSUIPC only clears the FSUIPC assignments. not the ones in MSFS. It is up to you to either create an empty profile in MSFS, or delete any assignments to a button/Switch/key/Axis in MSFS of assigning in FSUIPC. Other than that, I am not  sure what your issue is. Your log file looks ok, but shows you are using 7.5.0a. Please download and update to 7.5.0b.

Thats it from me for tonight....

John

 

 

[SMN204]

49 minutes ago, John Dowson said:

You need to copy this across to the MSFS2024 WASM persistence storage area.

In "MSFS2024 WASM persistence storage area:
C:\Users\xxx\AppData\Roaming\Microsoft Flight Simulator 2024\WASM
there are two folders:
- MSFS2020
- MSFS2024

Which one should I copy fsuipc-lvar-module folder with corrected FSUIPC_WASM.ini to?
Both?
 

[John Dowson]

13 minutes ago, SMN204 said:

In "MSFS2024 WASM persistence storage area:
C:\Users\xxx\AppData\Roaming\Microsoft Flight Simulator 2024\WASM
there are two folders:
- MSFS2020
- MSFS2024

Which one should I copy fsuipc-lvar-module folder with corrected FSUIPC_WASM.ini to?

Neither. You copy the fsuipc-lvar-module folder to the MSFS2024 Community folder, as described in the initial post. If you then want to add an  FSUIPC_WASM.ini file to the WASM persistence storage area, you need to first run MSFS2024 with the WASM installed, then the WASM storage area folder will be created under the ...\WASM\MSFS2020 folder. Then add your ini to the  ...\WASM\MSFS2020\fsuipc-lvar-module\work folder.

I don't understand why this is so difficult. This works in exactly the same way as with MSFS2020, it is just the folder names that have changed. I will update the documentation for this, once I have updated the installer...

 

[LeoSchoonbroodt]

46 minutes ago, John Dowson said:

@LeoSchoonbroodt Are you actually using the hvar files? These are only needed if using in lua or macro scripts (or via offsets). It is far easier to use presets, where these files are not needed., I am going to remove these as they are continually causing issues and are really not needed anymore. They are a hangover from the early days of MSFS2020.
If using hvars directly, switch to using presets instead. If using presets for hvars, stop going on about hvars and just talk about presets.

 Of course not. They are only there if you add them. I do install some hvar files, but they are installed with the FSUIPC WASM folder under your Community folder. As with the FSUIPC_WASM.ini, there is an order to how these are loaded, but please see the Advanced User guide - I am not going to explain this again when this has nothing to do with MSFS2024...
It all works in exactly the same way with MSFS2024 as with MSFS2020, only the locations have changed. I will update the documentation with the new locations for MSFS2024 before I release officially.

John,
I don't use the Hvar files anymore, today i use ipc.execCalcCode because there were more Hvars as get loaded from the files and in the past you advised to do it that way.
Just mentioned it as found that they were loaded under 2020 and NOT loaded under 2024 and don't know if it's related.
Also, i use a lot of lua files all using ipc.execCalcCode and don't feel to create all these presets and modify all my files when calculator code also should work.

You mentioned that it could use the files from persisted storage, that's why i mention that there are no hvar files in persisted storage.

Stays the question why it loads the hvar files for 2020 and not for 2024, used or not.

Also, it executes calculator code for a few seconds as you can see from the attached log and thereafter not anymore while in 2020 my lua can run AND function for hours and execute calculator code.

To be complete: i copied the FSUIPC7 folder for 2020 to a 2024FSUIPC7 folder containing the version 7.5b and copied the fsuipc-lvar-module folder from the 2020 community folder to the 2024 community folder.

Leo

 

 

 

[SMN204]

23 minutes ago, John Dowson said:

You copy the fsuipc-lvar-module folder to the MSFS2024 Community folder, as described in the initial post. If you then want to add an  FSUIPC_WASM.ini file to the WASM persistence storage area, you need to first run MSFS2024 with the WASM installed, then the WASM storage area folder will be created under the ...\WASM\MSFS2020 folder. Then add your ini to the  ...\WASM\MSFS2020\fsuipc-lvar-module\work folder.

🙂 I've already had it copied fsuipc-lvar-module folder to the MSFS2024 Community folder before!
And I've run MSFS2024 before.
And under ....AppData\Roaming\Microsoft Flight Simulator 2024\WASM  I see two folders  MSFS2020 and MSFS2024  😶
Probably 2024 was created when MSFS2024 was installed, and 2020 when it was started MSFS2024 after fsuipc-lvar-module
I got it, in the 2020  fsuipc-lvar-module\work folder  👍

[John Dowson]

21 hours ago, SMN204 said:

And under ....AppData\Roaming\Microsoft Flight Simulator 2024\WASM  I see two folders  MSFS2020 and MSFS2024

These are the WASM permanent storage areas created by MSFS2024.

@LeoSchoonbroodt Please don't embed your questions into quoted text, you are just making things difficult for me...I am not going to respond to that, sorry. But please check that you are not suffering from a WASM crash if you have issues where calc. code updates stop working. I have already posted enough information on this. Otherwise, please post any quertions unquoted...

That is it definitely it for tonight now - no more responses from me until late tomorrow or even later. Please review before posting.

John

One more piece of advise: if you are manually copying aircraft from MSFS2020 to MSFS2024 and have issues, please DO NOT post here. Try an included aircraft. I don't want to complicate things too much at this stage...

 

[kaha]

On 11/22/2024 at 10:53 AM, John Dowson said:

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

...

I flew the Carenado Cessna 182 RG in 2024 and it behaves differently from 2020. I would need different curves for aileron, elevator and rudder axis. How can I do that? Or is the only possibility to manually copy the FSUIPC folder? Or I could maintain 2 different .ini files and copy them before starting the sim.

I think this will also apply to some other aircraft.

Karl

[John Dowson]

1 hour ago, kaha said:

I flew the Carenado Cessna 182 RG in 2024 and it behaves differently from 2020. I would need different curves for aileron, elevator and rudder axis. How can I do that? Or is the only possibility to manually copy the FSUIPC folder? Or I could maintain 2 different .ini files and copy them before starting the sim.

If there is a difference in the aircraft names, you could use separate profiles. Otherwise its up to you - you can have a separate installation or have two ini files and copy/rename them before starting the sim.

[John Dowson]

@LeoSchoonbroodt

Quote

I don't use the Hvar files anymore, today i use ipc.execCalcCode because there were more Hvars as get loaded from the files and in the past you advised to do it that way.

Yes, that is preferred over using hvars directly.

16 hours ago, LeoSchoonbroodt said:

Just mentioned it as found that they were loaded under 2020 and NOT loaded under 2024 and don't know if it's related.

It is not related, but I will check this.

16 hours ago, LeoSchoonbroodt said:

Also, i use a lot of lua files all using ipc.execCalcCode and don't feel to create all these presets and modify all my files when calculator code also should work.

Presets and calculator code are basically the same thing - a preset is just a name associated to a calc. code string. And no, you shouldn't need to do that.

16 hours ago, LeoSchoonbroodt said:

You mentioned that it could use the files from persisted storage, that's why i mention that there are no hvar files in persisted storage.

They are only in that location if you add them there.

16 hours ago, LeoSchoonbroodt said:

Stays the question why it loads the hvar files for 2020 and not for 2024, used or not.

I don't know - as I said, I will look into this.

16 hours ago, LeoSchoonbroodt said:

Also, it executes calculator code for a few seconds as you can see from the attached log and thereafter not anymore while in 2020 my lua can run AND function for hours and execute calculator code.

If it stops working, I can only think that the WASM has crashed. When it stops working, do you see anything logged in the WASM log when you send the calc code?
If you exit MSFS, foes the WASM exit correctly, i.e. is the last line:

Quote

[ALWAYS]: <=============================== END OF PROGRAM ===============================>

If not, then the WASM has crashed. If it hasn't crashed, I need to know if the request is reaching the WASM or not.

[kaha]

Thank you. I think I will use the main FSUIPC installation for 2024 and make a copy for 2020. In a few months I will probably not use 2020 anymore..

[John Dowson]

1 hour ago, kaha said:

I think I will use the main FSUIPC installation for 2024 and make a copy for 2020.

If you do this, make sure that you update the EXE.xml for MSFS2020 to point to the copied folder, otherwise the main folder (where you installed using the installer) will be used.

[kaha]

Ok, I'll do.

[John Dowson]

20 hours ago, LeoSchoonbroodt said:

Is it possible that FSUIPC only looks for hvar files listed in layout.json as that would explain why the 2 not listed therein are not found?

It should process all hvar files in the Community\fsuipc-lvar-module\modules folder. Your log shows that there was no match of the hvar file names to the aircraft you were using ("Airbus H145 ADAC NoHMD"):

Quote

Fri Nov 22 16:52:22 2024   [DEBUG]: Found 7 *.hvar files under .\modules folder
Fri Nov 22 16:52:22 2024   [DEBUG]: Checking hvar file A320 for aircraft 'Airbus H145 ADAC NoHMD'
Fri Nov 22 16:52:22 2024   [DEBUG]: No match on aircraft name to hvar filename
Fri Nov 22 16:52:22 2024   [DEBUG]: Checking hvar file Asobo_C152 for aircraft 'Airbus H145 ADAC NoHMD'
Fri Nov 22 16:52:22 2024   [DEBUG]: No match on aircraft name to hvar filename
Fri Nov 22 16:52:22 2024   [DEBUG]: Checking hvar file DA40 TDI for aircraft 'Airbus H145 ADAC NoHMD'
Fri Nov 22 16:52:22 2024   [DEBUG]: No match on aircraft name to hvar filename
Fri Nov 22 16:52:22 2024   [DEBUG]: Checking hvar file DA40-NG for aircraft 'Airbus H145 ADAC NoHMD'
Fri Nov 22 16:52:22 2024   [DEBUG]: No match on aircraft name to hvar filename
Fri Nov 22 16:52:22 2024   [DEBUG]: Checking hvar file DA62 for aircraft 'Airbus H145 ADAC NoHMD'
Fri Nov 22 16:52:22 2024   [DEBUG]: No match on aircraft name to hvar filename
Fri Nov 22 16:52:22 2024   [DEBUG]: Checking hvar file Skyhawk for aircraft 'Airbus H145 ADAC NoHMD'
Fri Nov 22 16:52:22 2024   [DEBUG]: No match on aircraft name to hvar filename
Fri Nov 22 16:52:22 2024   [DEBUG]: Checking hvar file TBM for aircraft 'Airbus H145 ADAC NoHMD'
Fri Nov 22 16:52:22 2024   [DEBUG]: No match on aircraft name to hvar filename
Fri Nov 22 16:52:22 2024   [DEBUG]: 0 HVAR CDAs loaded from 0 files (max client data size=8192)
Fri Nov 22 16:52:22 2024   [DEBUG]: Hvars loaded

So this is expected. What do you mean by "the 2 not listed therein"? Did you add these files to the correct folder? The log shows only the 7 hvar files installed by the installer were found.

20 hours ago, LeoSchoonbroodt said:

Sorry forgot to mention:
several calculatorcode executions worked this time but stopped after a few seconds.

When you execute calc. code, and with Debug logging set in the WASM, you should see the calc code execution in the log, like this:

Quote

Fri Nov 22 16:52:56 2024   [DEBUG]: Calculator code executed: '(A:TRANSPONDER STATE:1, number) (>L:TransponderState)'
Fri Nov 22 16:52:57 2024   [DEBUG]: Calculator code executed: '(>H:H145_SDK_MASTERBRIGHTNESS_DEC)'
Fri Nov 22 16:52:58 2024   [DEBUG]: Calculator code executed: '(>H:H145_SDK_MASTERBRIGHTNESS_DEC)'
Fri Nov 22 16:52:59 2024   [DEBUG]: Calculator code executed: '(>H:H145_SDK_MASTERBRIGHTNESS_INC)'
Fri Nov 22 16:52:59 2024   [DEBUG]: Calculator code executed: '(>H:H145_SDK_MASTERBRIGHTNESS_INC)'
Fri Nov 22 16:53:03 2024   [DEBUG]: Calculator code executed: '(A:TRANSPONDER STATE:1, number) (>L:TransponderState)'

When it stops working, do you see anything logged? If not, then the WASM has crashed and you need to disable lvar scanning (see FAQ section). As the last entry in your log is this:

Quote

Fri Nov 22 16:53:07 2024    [INFO]: Scanning for new lvars: lvarScanFrequency=-15, last lvarScanTime=1732294372553, timeNow=1732294387715 (difference=15162)

It does look like the WASM has crashed when scanning for lvars.
Are you also using add-on scenery by any chance? How did you install the H145 - manually or via the MSFS2024 market place?

[LeoSchoonbroodt]

Hi John,

Yes further investigation confirms that the WASM crashed, NO === end of program ==== line.

I updated the WASM.ini LvarScanFrequency=0 and LvarScanDelay=10 as you advised in the FAQ and now i can fly the HPG Airbus 145 but now have the same problem with the HPG Airbus H160 (which has more complex textures).
So i updated the LvarScanDelay=16 and still have to test if that solves it but saw your answer and wanted to report first about the progress.

about the 2 added files Airbus H145.hvar and Airbus H160.hvar, yes i placed them in the modules folder next to the other files as i did also in FS2020 were they were loaded as the log shows 550 Hvars loaded.

will keep you posted about the progress.

Thanks for answering.

Leo
 

[John Dowson]

5 minutes ago, LeoSchoonbroodt said:

but now have the same problem with the HPG Airbus H160 (which has more complex textures).

So the WASM crashed on the initial lvar scan? That is very strange, and worrying - I haven't seen this before. Could you show we the FSUIPC_WASM.log file for this please.

7 minutes ago, LeoSchoonbroodt said:

So i updated the LvarScanDelay=16 and still have to test if that solves it

That will delay when the first scan will be performed, but if its crashing when initially scanning for lvars, it may not help. Unless its some sort of timing issue, and crashes if the lvar scan is done at certain stages of aircraft load / operation.

9 minutes ago, LeoSchoonbroodt said:

about the 2 added files Airbus H145.hvar and Airbus H160.hvar, yes i placed them in the modules folder next to the other files as i did also in FS2020 were they were loaded as the log shows 550 Hvars loaded.

I have checked this now - it doesn't pick-up hvar files added to the Community WASM folder' modules folder any more, as you noticed. It probably needs to be added to the layout.json file, as you say. I will ask Asobo about this and update the documentation accordingly. You can try adding them to the persistent storage area work folder instead - they should load from there (and that is the preferred place to add them anyway!).

John

 

[LeoSchoonbroodt]

Hi John,

No it didn't crash on the first lvar scan as you can see from the WASM.log i sent you, it even executes several calculator code statements before stopping responding.
So my idea of setting the LvarScanDelay higher was probably a misunderstanding from me, as this delay was long passed.

Nevertheless my flighttest with the H160 went very well, so i expect it's an intermittend problem or maybe something else caused the crash of the WASM for the initial first try with the H160.

Unfortunately i put that WASM logging back to info after the H145 worked and i did several good flights with it before concentrating on the H160.

I will put it on debug again so i have a valid WASM.log when it happens again

I will try to put the lvar files in the persistant store for sake of analysing, for me i now only use calculator code and some presets.

Leo

[John Dowson]

14 hours ago, LeoSchoonbroodt said:

No it didn't crash on the first lvar scan as you can see from the WASM.log

That was the log from the H145. You then set LvarScanFrequency=0 and said the WASM still crashed when loading the H160. It therefor seems like it crashed on the first lvar scan for this aircraft- but I need to see the mew/updated log to confirm.

14 hours ago, LeoSchoonbroodt said:

So my idea of setting the LvarScanDelay higher was probably a misunderstanding from me, as this delay was long passed.

This delay will always be long passed when the WASM crashes. This is just the delay between aircraft load and the first scan for lvars. You only need to increase this if the first scan does not return lvars that you are using directly by name or id (not in calc. code or presets), i.e. by adding to offsets, in lua or in macros.

14 hours ago, LeoSchoonbroodt said:

Nevertheless my flighttest with the H160 went very well, so i expect it's an intermittend problem or maybe something else caused the crash of the WASM for the initial first try with the H160.

Unfortunately i put that WASM logging back to info after the H145 worked and i did several good flights with it before concentrating on the H160.

I will put it on debug again so i have a valid WASM.log when it happens again

Ok. But this is also a known issue with the WASM, and is not related to the MSFS2024 release.

John 

[BlackLiverieZ]

Hi all,

I noticed the following. For ‘A Pilot's Life Chapter 2’ you need FSUIPC.

In MSFS 2020, everything works wonderfully.

But not so much with the beta in 2024.

The tool recognises the connection to the simulator, but the ‘Flight Stage’ point always remains red. Is there perhaps a solution for this?