wasm module crashed a350

[ROSSI ERIC]

Hello,

after 8 hours and 15 minutes of flight between NWWW and VTBS, this bug appeared. I had never experienced this issue before. I have 561 hours with your A350 on MSFS 2024. I performed an update of the FSLTL Traffic Injector just before the flight. Note that after stopping everything and restarting the game, everything worked normally again. Do you have any idea what might be causing this issue ?

Thank you very much.

 

 

[MITCH1988]

I am on xbox. I get this same issue in the -1000 and only in the -1000. I know i am going to have this issue because I notice on the flt pln page that the eta times at the bottom go all weird. They bug out and don't give me an ETA. Plus the Nav data on arrivals goes all weird as well and has some waypoints 6000nm away from actual flight plan. I have had to delete waypoints and manually add them and their specific restrictions. Plus the engine fans not spinning when the engine is running but that in itself is a console issue. The A350 in general was running fine until the 1.9.0 update. Since it has been hit and miss. Nav data not updating properly. Fan blades not spinning. Constantly having to download terrain data that doesn't save ever. it went from 1 of my best performing aircraft to the worst overnight. Such a shame because I absolutely loved flying it.

[IniSteve]

On 1/13/2026 at 9:31 PM, ROSSI ERIC said:

Do you have any idea what might be causing this issue ?

Do you have an autosave you can share? 

[ROSSI ERIC]

On 1/16/2026 at 9:21 AM, IniSteve said:

Do you have an autosave you can share? 

No, I do not have automatic saving enabled. The next day I tried to do a flight between VTBS and LFPG, and a second bug appeared after about 10 hours of flight: everything froze, it was impossible to disconnect the autopilot, etc. I only had engine sound and ATC still working. The aircraft was no longer following the flight plan. For your information, I had not activated FSLTL. I was forced to use (Alt + Del) to quit the game.

The following day I repeated the same flight and this time it worked. I was wondering whether the problem really came from the A350 or from MSFS 2024.