FSUIPC7 -> ini A300 Premium > FS2024 > Freeze

[Powie]

As mentioned here: https://forum.inibuilds.com/topic/24442-msfs2024-frozen-with-a300-600-premium/

I have played arround a little bit.... is there a chance for me to find out which function kills the aricraft/sim here?

[John Dowson]

From the comments this seems to be an issue with the FSUIPC WASM module and not FSUIPC itself, no?
If you remove the WASM and just use FSUIPC, does it work?
I don't know how FSUIPC could cause a plane to freeze, especially as the aircraft is not using FSUIPC or the WASM module.
Is the WASM module crashing or exiting correctly with MSFS?
Could you show me / attach your FSUIPC7.log and FSUIPC_WASM.log files from when this happens and after you exit MSFS / FSUIPC7.
Also please activate WAPI debug level logging in FSUIPC7 (Log->WAPI->Debug) and also in the WASM module (via the FSUIPC_WASM.ini file).

As you are a new forum user, you will have a very low limit for attaching files, so you may need to compress/zip them.

[Powie]

OK, I will start a session with this conditions and add the log file 👍

[aaronpriest]

I too am having this problem where the iniBuilds A300-600 Premium for 2024 freezes the sim and locks it up within 30 seconds of a cold and dark start. I've done quite a bit of testing, emptying the community folder, emptying the WASM folders, starting on the runway vs. cold and dark, etc. with iniBuilds support on their Discord. We've tracked it down to the fsuipc-lvar-module in the community folder. If I remove this folder, the plane is fine (except for an unrelated bug where exiting back to the main menu will hang the sim; Asobo is aware of this and has a fix but it is not pushed out to the sim yet). If I put the fsuipd-lvar-module folder back in the 2024 community folder, then the A300 will lock up within 30 seconds of a cold and dark start. I grabbed the latest FSUIPC WASM Module 1.0.7 listed on the website dated Dec. 6, 2024 and it does the same. I'm not sure I even need this folder though, as my Streamdeck buttons and things I use all seem to work fine without it. Any logs you want me to gather, or can you duplicate this on your machine? Assuming you have the A300 I guess.

[John Dowson]

I don't have the A300, and, as I said, I cannot see how the FSUIPC WASM module can freeze the sim, especially just for this one aircraft.
But I need to see the log files as mentioned in my last post before anything else.

22 minutes ago, aaronpriest said:

I grabbed the latest FSUIPC WASM Module 1.0.7 listed on the website dated Dec. 6, 2024 and it does the same.

What were you using before? Are you using FSUIPC7?

22 minutes ago, aaronpriest said:

I'm not sure I even need this folder though, as my Streamdeck buttons and things I use all seem to work fine without it.

You only need the FSUIPC WASM module installed for the following reasons:
  - using presets/hvars/lvars/calc. code functionality in FSUIPC7
  - if using any other add-on that requires it

John

[aaronpriest]

I do have FSUIPC7. I assume it installed the fsuipc-lvar-module that I removed. I checked the contents of the Dec 6th folder and compared it to my own. The FSUIPC_WASM.ini and manifest.json files were identical with my own, the same versions listed, but the contents of the modules subfolder were different. So I put the new fsuipc-lvar-module download in my community folder, started the sim, loaded in cold and dark in the A300, and it still locked up within 30 seconds or so. So it's definitely this folder I'd say.

iniBuilds has this to say:

Quote

 

FWIW, I've been doing many flights with FSUIPC (v7.4.18 and 7.5.0), SPAD.next,  GSX Pro and some sceneries, both FS24 compatible and from FS20 dragged over without any such issues (except hang on ending flight, as that's just the above known sim issue)

So we believe such instances are caused by conflicting add-ons or the sim not compiling/initiating WASM properly on load.

The fact it works on an empty community folder is confirmation of some potential conflict. As mentioned above, we can only ensure that the aircraft should work with respect to the core sim and in compliance with the SDK. The a300 should not affect functionality of another add-on when the above conditions are met.

Other add-ons, similarly, have to respect this and not change core sim functionality to the extent that it causes issues on another add-on. If they do, you need to report to said add-on's dev for resolution.

FSUIPC is a known conflict as seen in the thread above for some users (may be version dependent though, people who reported were on the newer Beta versions).

 

All I can say is that removing the fsuipc-lvar-module folder prevents the sim freeze within 30 seconds loading cold and dark with the A300, and I don't have the problem with any other planes, though I haven't tested EVERY plane in the sim yet, just many. I attached the FSUIPC7.log file, but I don't have any called FSUIPC_WASM.log in the C:\FSUIPC7 folder. Are there other places I should be looking?

Thanks!!!

 

 

 

FSUIPC7.log FSUIPC7_prev.log

[aaronpriest]

Oh, I should add, I did use the earlier beta version in this forum for a week or so until 7.5.0 was released, just in case those of us affected by this all happen to have that in common. I enabled debugging and I'll send over new log files in 10-15 minutes, waiting on the sim to reload...

Edited Thursday at 03:57 PM by aaronpriest

[aaronpriest]

Here is the FSUIPC7 log after enabling debugging. I can't find a FSUIPC_WASM.log although I did enable LogLevel=Debug in the FSUIPC_WASM.ini file.
 

FSUIPC7.zip

[kamix86]

Hello Gentlemen, I'll just join the conversation because I'd like to confirm that I have the same problem. I bought the plane a few days ago and haven't made a single flight with it. I created an account here specifically 🙂 I can't log it at the moment. After deleting the fsuipc-lvar-module folder from community, everything works fine. Several users on discord iniBulids had this problem and everything was generated by the folder.

Edited Thursday at 04:15 PM by kamix86

[John Dowson]

27 minutes ago, aaronpriest said:

but the contents of the modules subfolder were different.

In what way? They should have been the same...

InBuilds did say:

27 minutes ago, aaronpriest said:

FWIW, I've been doing many flights with FSUIPC (v7.4.18 and 7.5.0), SPAD.next,  GSX Pro and some sceneries, both FS24 compatible and from FS20 dragged over without any such issues

so they have no issues with the FSUIPC WASM.

27 minutes ago, aaronpriest said:

but I don't have any called FSUIPC_WASM.log in the C:\FSUIPC7 folder. Are there other places I should be looking?

Yes - in the WASM persistent storage area, under your AppData\Roaming folder. See the Advanced User guide (WASM section) if you don't know where this is - the details are there. Please only attach this file after exiting MSFS.

Your FSUIPC7 log files look ok.

Do you have anything else om your Community folder? If so, have you tested with these removed?

Does this occur in MSFS2024 only, or also in MSFS2020?

Edited Thursday at 04:18 PM by John Dowson
Further info added

[aaronpriest]

iniBuilds DOES have issues with the FSUIPC WASM, but not FSUIPC installed by itself without the fsuipc-lvar-module folder. We were trying to figure out if we had to also uninstall FSUIPC completely, or SPAD.next (which I don't have) or GSX Pro (that I do have). We were troubleshooting a lot of things. The commonality seems to be specifically the fsuipc-lvar-module folder in the community folder.

As far as the modules subfolder differences, the one from Dec. 6th has an Asobo_C152.hvar file that I did not have previously (maybe from installing the beta of FSUIPC?). The rest of the files look the same for date and size, just that one C152 file being different. I don't think that matters because both folders acted the same, whether the C152 file was there or not.

I found the FSUIPC7 for Advanced Users.pdf and I've been reading it. It mentions AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\fsuipc-lvarmodule\work for 2024. I have a C:\Users\Aaron\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024 folder, but I do not have a fsuipc-lvarmodule subfolder there. I only have fcr-embedded and inibuilds-aircraft-a300. Maybe because I'm not actually using it so it's not creating those files and folders?

I have tested with a completely blank community folder and only the inibuilds-aircraft-a300 and fsuipc-lvar-module folders in my community folder under 2024. If both are there, the sim locks up with cold and dark start of the A300. If fsuipc-lvar-module is removed, it does not.

I have not tested under 2020 because I bought the "A300-600R Premium for MSFS 2024", it's native to 2024 and I don't own the older 2020 version. I don't know which specific versions others might be using though.

Hope that helps!

 

 

[John Dowson]

2 minutes ago, aaronpriest said:

I found the FSUIPC7 for Advanced Users.pdf and I've been reading it. It mentions AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\fsuipc-lvarmodule\work for 2024. I have a C:\Users\Aaron\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024 folder, but I do not have a fsuipc-lvarmodule subfolder there. I only have fcr-embedded and inibuilds-aircraft-a300. Maybe because I'm not actually using it so it's not creating those files and folders?

That is wrong -  for Steam installs, its under:
   AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2020\fsuipc-lvar-module\work
The folder will only be there if you are using the FSUIPC WASM module.

4 minutes ago, aaronpriest said:

have not tested under 2020 because I bought the "A300-600R Premium for MSFS 2024", it's native to 2024 and I don't own the older 2020 version. I don't know which specific versions others might be using though.

Ok, I didn't realize it was 2024 only...

4 minutes ago, aaronpriest said:

Hope that helps!

Well, its the FSUIPC_WASM.log file that I need to see, and attached only once MSFS2024 has exited.

[aaronpriest]

I don't have the Steam version, I have the Microsoft Store version. Probably this can't be resolved until Asobo releases the fix to the sim locking up when going back to the main menu (a second unrelated problem), so the sim can NEVER exit cleanly with the A300 without being terminated from task manager, thus your WASM log file will never get created. I could use another plane of course, and then exit the sim cleanly and see if these files get created. But I've been doing that with a multitude of planes since installing the sim on launch day, and that folder and log file still don't exist, so I guess that means I'm not using any WASM related things, and thus I probably don't need the fsuipc-lvar-module folder in the community folder at all.

[John Dowson]

1 minute ago, aaronpriest said:

I don't have the Steam version, I have the Microsoft Store version.

Then the log file should be here:
    AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2020\fsuipc-lvarmodule\work
i.e. under MSFS2020 not MSFS2024. There is an error in the document that I will correct.

3 minutes ago, aaronpriest said:

thus your WASM log file will never get created.

It will get created, as it is created when MSFS starts the WASM during start-up. However, if you kill the sim it won't exit correctly.

4 minutes ago, aaronpriest said:

I could use another plane of course, and then exit the sim cleanly and see if these files get created.

No point in doing this....

5 minutes ago, aaronpriest said:

But I've been doing that with a multitude of planes since installing the sim on launch day, and that folder and log file still don't exist,

Of the FSUIPC WASM module is installed, that folder will/must exist. You are just looking in the wrong place...

6 minutes ago, aaronpriest said:

so I guess that means I'm not using any WASM related things, and thus I probably don't need the fsuipc-lvar-module folder in the community folder at all.

The folder and log file will exist regardless of whether you use the WASM or not, if the WASM is installed.

[John Dowson]

10 minutes ago, aaronpriest said:

Probably this can't be resolved until Asobo releases the fix to the sim locking up when going back to the main menu (a second unrelated problem), so the sim can NEVER exit cleanly with the A300 without being terminated from task manager, thus your WASM log file will never get created.

But you don't have to go back to the main menu to exit the sim - use the FSUIPC7 menu option MSFS->Exit

[aaronpriest]

Ah, OK, I DO have a C:\Users\Aaron\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2020\fsuipc-lvar-module\work folder. The documentation said WASM\MSF2024 so I never checked the 2020 folder. Here is the WASM log file! Note, this was after terminating the sim via task manager because it locks up of course, but hopefully there's something interesting here that's helpful.

FSUIPC_WASM.log

[aaronpriest]

So, more news, iniBuilds just confirmed that they DO have the fsuipc-lvar-module folder in their community folder and working fine, and they tested FSUIPC 7.4.13 through 7.50, but they NEVER had the beta installed. I did. And apparently so have several of the other people affected, but we have no way of knowing if it is ONLY those that tested the 7.5.0 beta or not.

[John Dowson]

5 minutes ago, aaronpriest said:

The documentation said WASM\MSF2024

Yes, that is an error and will be corrected in the next release, sorry.

5 minutes ago, aaronpriest said:

Note, this was after terminating the sim via task manager because it locks up of course, but hopefully there's something interesting here that's helpful.

The log file shows that the WASM crashed. Try disabling lvar scanning, see the following FAQ entry: 

 

Basically you just need to set the WASM ini parameter LvarScanFrequency to 0. In fact. the latest release should have this already set, but may be overridden if you have an FSUIPC_WASM.ini file in your persistent storage area. If you do, remove that or change/update there. 

I don't see how a WASM crash can freeze the sim though, unless the A300 is using the WASM...

John

[aaronpriest]

iniBuilds says, "A300 is a WASM aircraft.Its not dependent on FSUIPC WASM though for any of its features."

I don't have a FSUIPC_WASM.ini file in persistent storage. I'll change the LvarScanFrequency on community folder file and get you a new log once the sim starts again, give me 15 minutes or so... haha!

[aaronpriest]

iniBuilds has LvarScanFrequency=0 on the fsuipc-lvar-module folder created by the FUSIPC7 installer (version 7.5.0), but is missing the Asobo_C152.hvar file. I had deleted the fsuipc-lvar-module folder and downloaded the Dec. 6th version from the website, which does include the Asobo_C152.hvar file, but LvarScanFrequency=-15 in that download. I suspect the beta of 7.5.0 also had it set to -15? At any rate, changed it to 0 and so far the sim has not locked up on a cold and dark start! It's only been a couple minutes so far, but it usually was within 10-30 seconds before. Here is an updated WASM log file with debugging enabled.

FSUIPC_WASM.zip

[John Dowson]

3 minutes ago, aaronpriest said:

had deleted the fsuipc-lvar-module folder and downloaded the Dec. 6th version from the website

What website? Use fsuipc.com, as the zip file may have been cached if using the download links in this forum. I have checked the zip file again and it is definitely set to 0.

[aaronpriest]

I linked it in my first post: FSUIPC WASM Module 1.0.7 dated December 6th 2024. I grabbed that this morning thinking it might be newer than the folder I had. The only difference with the folder I had was the new Asobo_C152.hvar file that I was missing. Both this file and my current one have LvarScanFrequency=-15. I assume the beta of 7.5.0 probably had the same and that's how mine got set, and upgrading to the final public release of 7.5.0 doesn't overwrite that file if it already exists?

[aaronpriest]

Well, another affected user in the iniBuilds Discord group also has LvarScanFrequency=-15, although they said they never installed any beta versions, nor downloaded the WASM module separately from your website. So I'm not sure what set some of ours to that.

[John Dowson]

24 minutes ago, aaronpriest said:

I linked it in my first post: FSUIPC WASM Module 1.0.7 dated December 6th 2024.

Ok, I have corrected it there. But you only need to download that if not using FSUIPC7.

25 minutes ago, aaronpriest said:

I assume the beta of 7.5.0 probably had the same

Yes, I updated this after the beta, or maybe in the final beta.

26 minutes ago, aaronpriest said:

and upgrading to the final public release of 7.5.0 doesn't overwrite that file if it already exists?

It will overwrite, but I think this was changed a day after the initial release, so if you downloaded early it would have had the old value.

15 minutes ago, aaronpriest said:

Well, another affected user in the iniBuilds Discord group also has LvarScanFrequency=-15, although they said they never installed any beta versions, nor downloaded the WASM module separately from your website. So I'm not sure what set some of ours to that.

As I said,  I think the initial release still had this set as -15. As this was causing issues, especially in MSFS2024, I decided to make 0 the default, but I didn't release/update the version number for this change.

If this fixes the issue, could you post this on the IniBuilds forums so that anyone who has this issue can check that setting.

I still don't understand how a WASM crash can cause the a/c to freeze though, very strange....

John

 

[aaronpriest]

Yeah, I've never downloaded the WASM module separately before, not until this morning when troubleshooting. I did test downloading FSUIPC7 from the website and reinstalling it this afternoon, but it did not overwrite the FSUIPC_WASM.ini file nor change it from -15 to 0. I had to change it manually. Apparently this has happened to a few other people in the Discord group as well, but we know what to change and where to change it now. :-)