Inibuilds A350 Master WASM Crash Thread v1.2.5 FS2024

This thread will be the new location for all WASM Crashes relating to the Inibuilds A350-900/1000 for Microsoft Flight Simulator 2024

Below this message will be where users can upload their WASM Crashes pertaining to the current version of the A350.

NOTES: If you do not see orange expectations screens on your displays or "WASM exception in X gauge" in the developer console it is not a WASM crash. The "sim-freeze" is a separate event that is tied to something on the server side which we are investigating with Asobo.

All WASM Crashes existing in this thread will be removed following the release of a new update.

i.e. Any Crashes identified in Inibuilds A350 v1.2.5 will be removed from the post following the release of v1.x.x and so forth.

Please ensure that when posting WASM crashes you post the WASM log from the in-game console alongside any media (photo/video) and a brief description of what you were doing leading up to the crash. Instructions on what to do are located in this thread - 

Any posts not following this format are subject to deletion.

Thank you

Now im starting to believe this might be on MSFS24's end

 

• Aircraft: A350-900 (Default Cabin)
• Simulator: FS2024
• Version: 1.2.5
• Navdata Method: NAVIGRAPH
• OFP: YSSYVVTS_PDF_1777082737.aceac65e.pdf
• WASM Error: N/A
• Specs: Intel i7-9700 | RTX3050 | 32GB RAM
• Autosave File:  1777097536.bin

 

 

• Aircraft: A350-1000
• Simulator: FS2024
• Navdata Method: NAVIGRAPH
• OFP: Attached
• WASM Error: Attached
• Specs: 9950X3D, 5090 32gb, 4TB storage, 192GB memory
• Autosave File:  Don't have one, screenshot proof attached
• WASM: Error whilst completing departure data input. Clicked on wind when it happened.

YSSYVHHH_PDF_1777251542.e7e7526c.pdf

Never had orange screens on the A350 before until now. Was literally js switching views 😕

• Aircraft: A350-900 (Default Cabin)
• Simulator: FS2024
• Version: 1.2.5
• Navdata Method: Sim Default
• OFP: RKSILIRF_PDF_1777435733.51a35dc3.pdf
• WASM Error: WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty
• Specs: Intel i7-9700 | RTX3050 | 32GB RAM
• Autosave File:  1777443859.bin

 

Hello, please help me. 
A few days ago, I cleared the WASM folder. Then I did a few excellent flights. And now there are problems again. What to do? Clear folder?
I just flew and did nothing.


 

• Aircraft: A350-900 v1.2.5
• Simulator: FS2024
• Navdata Method: NAVIGRAPH
• OFP: Pinned it
• WASM Error: Pinned it
• Specs: CPU: 13400F, GPU: 5070 and RAM: DDR5 32, system: win10
• Autosave File:  NO

UUDDOMDB_PDF_1777437434.4c43aa2b.pdf 29.04.2026.txt

Hello. I cleaned the WASM folder. I flew a new one. I flew to the arrival airport, was on approach, and WASM hovered again. But there was no error in the console already related to WASM.

I entered the weather and pressure in the arrival section of the FMS. After a few seconds, I noticed that WASM was frozen....

 

 

 

 

29.04.2026.2.txt UUDDOMDB_PDF_1777454645.e281db1b.pdf

1. Aircraft: A350-900

2. Simulator: FS2024

3. Version: 1.2.5 iniManager

4. Navdata Method: NAVIGRAPH

5. OFP: KMSP to RJTT

6. WASM Error: alid script (command not found - perhaps a space is missing or there's an extra space?): "="

7. Specs: i9-14900k, 9050 XT, 64gb

8. Autosave File:  1777750293.bin

KMSPRJTT_PDF_1777710942.466110ff.pdf 1777750293.bin