Yes, see here too.
Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure itâs a bug, please first report in User Support Hub.
3 tags are required - add them in the tag section next to the title above:
-
One for aircraft (start typing in your aircraft name in the tag section and pick correct option)
Feel free to delete this quote section after adding your appropriate tags.
ISSUE DESCRIPTION
Description of the issue:
V 1.6.25.0
A321LR Inibuilds, start flight at EGLL runway 27R, parking brake on, TAB for EFB.
Immediately after clicking âRequest from Avionicsâ, ALL WASM displays crashed with an orange background.
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every IniBuild A321LR flight.
Shutdown SimAppPro, reboot sim, remove all peripherals, identical crash every time.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
-
Free flight, IniBuilds 321LR, EGLL, runway 27R, engines running, parking brake on
-
Open the EFB
-
Click on âRequest From Avionicsâ
-
Immediate WASM module crashed (orange) for every display in the cockpit
Once, after about 10 WASM test crashes, there was a CTD.
Fenix A320 does not cause a WASM crash.
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using, if relevant:
WinWing FCU and MCDU (SimAppPro), TCA Quadrant.
Still crashes with peripherals and driver removed.
[PC Only] Are you using Developer Mode or have you made any changes to it?
No
[PC, MSFS 2020 Only] Are you using DX11 or DX12?
[PC Only] What GPU (Graphics Card) do you use?
GTX1080TI 11GB VRAM
[PC Only] What other relevant PC specs can you share?
MobiFlight installed but not running.
MEDIA
My A340 is unflyable in the last few betas. I just doesnât load everything correctly. It doesnât matter if itâs streamed or downloaded and every airport I try is the same. Iâve tried reinstalling MSFS, tried removing everything from community to no avail.
Same result every time orange instruments and a levitating aircraft.
You need to start at the gate right now in Su4, there is an issue where the WASM doesnât initialize properly on runway and air starts
Ok thanks Iâll try that. I always start C&D and this started happening after I powered up at the gate. With trying all the various possibilities reinstalling etc I started spawning on the runway (for quickness) where it happens 100%. Iâll give it a go from C&D again and see what happens.
Just got first my WASM crash tuning LSZH rwy 28 approach, the same as reported above, with SU3. Nothing new, just keeping topic alive. Hope that SU4 can help because I am running empty for planes that work, actually (777 doesnât, Fenix requires HIGH textures - too costly on fps for my VR and photogrammetry, 737 not ready yet, A350 too heavy on FPS probably and same issue, ifly max not ready for VR).
On Xbox series x SU4, Two different flights in inibuilds A320 and A330 resulted in WASM crashes during a flight from KPHX to KSAN just before arrival at KSAN. This might be related to making changes to the arrival in the MCDU.
Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure itâs a bug, please first report in User Support Hub.
3 tags are required - add them in the tag section next to the title above:
-
One for platform (ms-store, steam, xbox, playstation, or xcloud)
-
One for aircraft if related (start typing in your aircraft name in the tag section and pick correct option)
Feel free to delete this quote section after adding your appropriate tags.
ISSUE DESCRIPTION
Description of the issue:
In SU4, I observe WASM crashes frequently in the inibuilds A320 As well as the A330.
I created a flight plan from KPHX to KSAN and up until I was close to KSAN the flight was going well. But I overshot the airport and while attempting to make a âdirect-toâ to a previous waypoint and change the FCU speed and altitude, every cockpit display turned orange with a message âWASM module crashedâ
I use the following controllers⊠kid, mouse, velocity 1 yoke, throttle quad and rudder pedals. I also use a MIAP kbd extension, but it is not used in this simulation
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
This happened during two consecutive flights using same flight plan (A320, the A330)
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
-
create simbrief OFP from KPHX rwy 7L to KSAN rwy 27 RNAV Z and program into FMC
-
Takeoff and fly past KSAN, then try to program a direct-to waypoint in the FMC.
-
In my simulation the aircraft had a bit of trouble trying to fly it and while messing with the auto pilot FCU to change altitude and speed it eventually gave the WASM crash
[PC ONLY] FAULT BUCKET ID
If you experienced a crash on PC, sharing your Fault Bucket ID would be extremely helpful. You can learn how to find that ID here: How to find your Fault Bucket ID after a crash [PC]
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using, if relevant:
[PC Only] Are you using Developer Mode or have you made any changes to it?
[PC, MSFS 2020 Only] Are you using DX11 or DX12?
[PC Only] What GPU (Graphics Card) do you use?
[PC Only] What other relevant PC specs can you share?
MEDIA
Please add a screenshot or video of the issue occurring.
WASM crash in the A321LR (Inibuilds) during STAR and RWY switch.
Since SU4, I have constant WASM module crashed in A400M just after I request the Simbrief FPL from the MCDU. I am on PC.
Same here yesterday from PHNL to PHKO with the A330 on PC SU4, while changing approach procedure by pushing 1R on the MCDU. Managed to divert and succesfully land in PHOG. It felt like a emergency situation with total system loss.
Never had WASM crashes before, but since SU4 all the timeâŠ..Semms to be a SU4 problemâŠ
The A330âs never gave me grief either in SU3 or SU4 release. The A321 though, without fail. If I try to add or change anything in the MCDU once the flight has started, such as approach procedure, WASM crash guaranteed. I would have been happy with the INI A321 default, but with these crashes, itâs virtually guaranteeing a purchase for FENIX!
This is happening to me now on PC Steam FS2020 with the A300.. itâs so frustrating.
The same to me - FS2024 with iniBuilds A300, 80 nm short of LSZH during STAR and approach data entering to FMC.
This morning A330-300. Wasm crash while setting MCDU (for secondary flight plan) in the air. Please find a solution to this issue.
Not necessarily an XBox issue. I had this happen on FSS E190 this morning, Iâve also had it (once) on the JF RJ. Iâm on PC too, so itâs really an SU4 thing I think.
I experienced the same (can repeat the steps). In the cases where I did experience the crash it was for flights where I introduced a âhold-patternâ into the approach.
Here is the routing for the flight
Route
EDDF**/25C N0380F230 CIND3F CINDY Z74 HAREM T104 ROKIL ROKI1B EDDM/**26R (created with SIMBRIEF)
I also did see the behaviour for the RW 08R approach for EDDM.
Here are the steps I did:
Shortly before reaching the waypoint âROKILâ I inserted the Holding pattern via MCDU. A320neo flies the pattern. On MCDU I selected âImm Exitâ, A320neo leaves the pattern and continues on route to the next waypoints for about 2-4 minutes (did not have a stopwatch running). After this timeframe the error with âWASM crashâ appears.
In the attached pictures you can see the PFD with the Hold-pattern, the MCDU after I left the Holding pattern and the error message on the different displays in the cockpit.
The same flight/routing without the holding pattern finishes without the crash.
Hello,
I have the same issue. After spending hours on MSFS 2020, I finally managed to get a proper RTX graphics card to run FS 2024. I start the game, launch a free flight, choose the A320, go into the FMS and⊠WASM crashes.
This is unacceptable.











