aaronpriest
-
Posts
16 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by aaronpriest
-
-
I analyzed the Install_FSUIPC7.zip file I downloaded about 40 minutes ago. The date/time on it says today at 1:20PM when I downloaded it. The SHA1 hash for it is EBAA0FAF4DB41A7E0EA25C2B9A453C647F8A6942.
I suspect it's a browser cache of an older file though, because when I poke around a bit in it with 7-zip and I go to the Install_FSUIPC7.zip\Install_FSUIPC7\Install_FSUIPC7.exe\29.zip\fsuipc-lvar-module.zip\fsuipc-lvar-module\ folder and look at FSUIPC_WASM.ini it still says -15. But the LogLevel=Debug didn't change back to =Info either, nor did the date/time of my file change when uninstalling and reinstalling FSUIPC7 either. For what any of that is worth...
-
Yes, I used the top link on the home page of fsuipc.com.
-
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. :-)
-
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.
-
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?
-
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.
-
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! -
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.
-
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.
-
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.
-
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!
-
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.
-
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...
-
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:
QuoteFWIW, 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!!!
-
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.
FSUIPC7 -> ini A300 Premium > FS2024 > Freeze
in FSUIPC7 MSFS
Posted
Well, I downloaded it again with a different browser that I've never used, in incognito mode as well just to be certain, and I still got the same file hash and the same -15. So I dunno, maybe there's some CDN regional caching going on for my location? Doesn't really matter, mostly just curiosity at this point. ;-)