Happened to me after 5 minutes of my very first takeoff. Everything frozen. FlyByWire also very broken. A year later and still no fix?
If I understood the last Devstream correctly, there is no fix in sight:
They were talking about WASM crashes - which is related to this issue if Iâm not wrong - and the answer to the question of the community was in the direction of âwe might have an idea about what we could do about it, but we have to think about it further and go testing the theoryâŠâ.
Very vague for a high-voted issues since an eternityâŠ
So my drastic and probably not popular theory is:
solving it on Inibuilds side would be a lot of effort due to rewriting basics of the Airbus codes.
Microsoft signed off the products as buggy as they are due to the insufficient QA testing, but still expect Inibuilds to solve it âfor freeâ.
But Inibuilds is not willing/able to invest further of itâs limited capacity without payment.
And also MS/Asobo doesnât want to assign too much own capacity on solving the issue inside FS2020/2024, as they are struggling to get it out of alpha state still 9 months now after release.
So here we are, disappointed simmers, left with an unusable fleet of nice Airbus planes. 
I havenât used any of them for months now due to this issue.
3 Likes
Iâve been using the A320 v2 without WASM crashes in SU2. After SU1, I experienced crashes, but only 1 or 2 since SU2. I also clear the WASM folder every time I clean the MSFS2024 cache, shader cache, etc etc.
MSFS 2020
I caught the same bug with pmdg 737 few days ago.
So the problem isnât with the planes.
one thing that is still completely repeatable for me is the wasm crash when selecting the ils28 or ils34 in zĂŒrich and today i also had a crash when copying the flight plan into the secondary flight plan. This was on the a330 and just kills any joy in flying long hauls in these planes.
4 Likes
i dont have freeze , i have lagg or delay in Displays and MCDU ! SU16 !
Sad buyers of A350âŠ
I had the exact same problem without touching the MCDU. I did make any change in the flight plan, arrival runway, nothing. It just occurred at 400 ft AGL (indicated on RA). Weather radar was ON and FD was on APPR mode (CAT 3 SINGLE), I think this happened when switching to LAND on the FMA, not sure. I will try to try again without WX radar to see if it is the culprit.
Fortunately I could land, this didnât ruin my flight, but I couldnât start the APU and stop the engines, I guess the WASM code has fully crashedâŠ
I just experienced this issue. For me, I was flying KLAS to KXTA. The freeze happened when I got a terrain warning flying over the hills. It appeared to freeze the moment the terrain warning went off. Possibly relevant, I had weather on and the terrain display on. Has anyone found a workaround?
Can somebody explain it to me: is this such a rare bug that Asobo does not care? If yes, why I get it every flight with their A320? How to avoid it?
1 Like
I would suspect that as it hasnât very many votes, it isnât a common occurrance.
I personally have never had it happen.
If you havenât, I would suggest checking for obvious causes, such as a mod conflict, may be some help.
interact with the mcdu as little as possible
1 Like
I use no mods. It happens in stock config. And also it does not happen with non-Asobo aircraft.
1 Like