I have been slowly migrating into FS2024 and have been slowly applying tweaks making it look and run better.  When I pick up a new PC in the Fall sometime I plan to fully retire FS2020 and hopefully by then just about everything I have in FS2020 will work in FS2024.  Like it or not FS2024 is the direction most developers are heading. 

During testing and just general running in FS2024 I have been doing a lot of flights in the default Inibuilds A330 and A320 Series aircraft.  Pretty much 100% of the time within 30 to 45 minutes into the flight I loose the ability to use instrumentation in the cockpit and the plane just turns turtle and will crash.  It pretty much ruins an otherwise wonderful experience with the plane.  Doing some research this is what as referred as a WASM crash and unfortunately these models are plagued by it.  Exact causes seem to be unknown and blame is placed on both Inibuilds and Asobo but it but others have experienced it with other models occasionally.  Interestingly in my experience its only the default Inibuilds aircraft.  Even Inibuilds own A350 is not really an issue on my system but it is for some apparently.  I never had a WASM crash on the Fenix A320 series planes either but some have.  

Anyone find a fix for the constant WASM crashes? 

I suspect that raw system performance might have something to with it.  The latest state of the art systems might suffer less from it whereas an older system that is already being maxed out might have more of a problem with it.  However in my research I can't find any real definitive answer.  Some have claimed more system memory seems to have solved the issue but that is not definitive either.        

      

Have you tried deleting the wasm folder for the desired airbus folder and letting the system rebuild a new one? You never mention if you're using the Beta version of 2024 or the SU3 version.

I came accross such a situation along the biggest flight I was trying to make in the default A333...

Autoflight, FCU, MCDU all got frozen and I couldn't control the aircraft from there on, ending on a Crash 🥴

5 hours ago, longhaul747 said:

I suspect that raw system performance might have something to with it.  The latest state of the art systems might suffer less from it whereas an older system that is already being maxed out might have more of a problem with it.  However in my research I can't find any real definitive answer.  Some have claimed more system memory seems to have solved the issue but that is not definitive either.        

What hardware are you running right now?

Write now I am running SU3 standard release version.  I have not participated in the betas.  Back in the day if you installed a beta and messed something up during the real update you had to reinstall the whole sim.  I think they fixed this but it happened way back with FS2020 during one of the betas.

I have an 2021 build with an Intel I7 10700 with 32GB of ram and a GeForce 2070 Super with 2 1TB hard drives one of them being an SSD.  Its a bit dated now but still runs MSFS incredibly well.  Plan to upgrade at some point next winter if I find a deal. 

I have never cleared the WASM folder for the A330.  I remember looking for it but could not find it.  Its well hidden somewhere.  I did clear it for the Inibuilds A350 one time and I think that helped.  It was WASM'ing after one of the updates and shortly after Inibuilds came out and said to clear the WASM folder for the A350. 

 

 

6 minutes ago, longhaul747 said:

Write now I am running SU3 standard release version.  I have not participated in the betas.  Back in the day if you installed a beta and messed something up during the real update you had to reinstall the whole sim.  I think they fixed this but it happened way back with FS2020 during one of the betas.

I have an 2021 build with an Intel I7 10700 with 32GB of ram and a GeForce 2070 Super with 2 1TB hard drives one of them being an SSD.  Its a bit dated now but still runs MSFS incredibly well.  Plan to upgrade at some point next winter if I find a deal. 

I have never cleared the WASM folder for the A330.  I remember looking for it but could not find it.  Its well hidden somewhere.  I did clear it for the Inibuilds A350 one time and I think that helped.  It was WASM'ing after one of the updates and shortly after Inibuilds came out and said to clear the WASM folder for the A350. 

 

 

Just a little update...I found the WASM folder for the A321 and A330 and cleared it.  It only had one file in it related to the throttle.  

It will take some trial and error to see if it makes any difference.

 

2 hours ago, longhaul747 said:

Just a little update...I found the WASM folder for the A321 and A330 and cleared it.  It only had one file in it related to the throttle.  

It will take some trial and error to see if it makes any difference.

 

I’ve recently started experiencing the same issue with my throttle on several third party aircraft as well, including GA and bush planes. I haven’t figured out what the core issue is either and I tried deleting all WASM folders. 

It is a sim-related problem that has no solution at the moment (judging by Asobo's responses). For some reason ini's planes, both payware and default seem the most affected but I had this problem in the PMDG 777 a couple weeks ago as well. In one of the latest streams Jorg stated that they are aware of the problem but it has no clear solution - wasm just gets full of small errors and just stops working at some point, this rules the possibility to take small snapshots of the wasm situtation during flight to restore a previous "save" as it will just crash again. Inibuilds tries to patch the a350 solving single instances that lead to a wasm freezes but it isn't a permanent solution either as even on the latest patch it can and will crash. I had such crashes on ground, while meddling with the fmc, while in cruise just looking straight ahead and so on and so forth. I just stopped using any ini related planes for the time being. Oh, forgot to add - I had these crashes on two completely different computers so it isn't system or hardware related.

Edited September 18, 2025Sep 18 by dzmitry

I (and others) have also had this problem in the Maddog MD-80.  So agree it's a sim WASM issue. 

these wasm errors and the fiddlely UI is the exactly reason im not going anywhere near ms24

23 hours ago, longhaul747 said:

I suspect that raw system performance might have something to with it.

Nope. I hardly had a state of the art system when the A350 was released and only ever suffered two WASM crashs from then until now.

In my opinion its the one thing that is keeping me from moving forward with FS2024.  3 times in the past week I tried to recreate the Hawaiian A330 flight they have been randomly doing for real between SEA and ANC.  Every bloody time about 30 minutes into the flight over Vancouver Island the plane goes belly up and crashes into the island.  I can still manually control the plane with my joystick but all instrumentation is frozen and no switches work. 

Its to randomly happen if you touch the FMC during the flight in my case.  Oddly when FS2024 first came out I was doing some random Delta A330 flights and never experienced the issue.  It seems the WASM crashes started a bit later for me but are now pretty much 100% of the time in the Inibuilds stock airplanes. 

I my opinion its a critical error that needs to be fixed!  

  

I get the occasional wasm crash in 2020, so this isn’t just a 2024 issue.

I found something weird too. I have a WASM module for retrieving Lvars from the IniBuilds A350. I have an MSFS 2020 and an MSFS 2024 version. The MSFS 2020 version is working perfectly when I load the WASM module from the Community folder or from the Developer mode (as a project). However for the 2024 version, the module works gread when I load it from the Developer mode, but gives me wrong or zeroed Lvar values when i load it from the Community folder. Besides, if I load the module from the Developer mode (in 2024), while it is already loaded from the Community folder, it works well again. Not sure where is the problem MSFS SDK or IniBuilds A350. My feeling is that it is an MSFS issue (TBC).

Currently 10 hours into a 14 hour A330-200 flight no issues so far. I am on the SU4 beta though.

Edited December 4, 2025Dec 4 by Tuskin38