Inibuilds A350 Master WASM Crash Thread v1.2.6 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.6 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

• Aircraft: A350-900

• Simulator: FS2024

• Navdata Method: NAVIGRAPH

• OFP: PFD Attached

• WASM Error:

  WASM: Error during HUD_gauge_update execution. Error code : 0xc000001d

  WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty

• Specs: i7 14700f, RTX 5080, 16gb DDR4 RAM

• Autosave File:  N/A

I was trying to reload the approach ILS 04L into EKCH as after few vectors from the ATC, it doesn't say the arrival/approach type on top of the ND. Then the crash happened once i clicked on ILS04L on the arrivals page.

WSSSEKCH_PDF_1779843119.8e8108bd.pdf

1. Aircraft: A350-900

2. Simulator: FS2024

3. Navdata Method: MSFS

4. OFP: PFD Attached

5. WASM Error: Imported flight plan and was about to enter W&B Data.

6. Specs: Intel(R) Core(TM) i9-10900KF CPU @ 3.70GHz (3.70 GHz), 64gb DDR4 RAM, ASUS TUF Gaming GeForce RTX 5080 OC90YV0M30-M0NA00

7. Autosave File:  attached1780165438.bin

LFPGLSZH_PDF_1780163962.b533e496.pdf

• Aircraft: A350-900

• Simulator: FS2024

• Navdata Method: NAVIGRAPH

• OFP: PFD Attached

• WASM Error:

• Specs:AMD Razon 7 9800 X3D 8-Core 5.2Ghz, RTX 5070ti, 2x32gb DDR5 RAM

• Autosave File:  1781523798.bin , albeit this was the previous file prior to crash.

I cruise after a 2 hour flight EGCC-LIRN via SimBrief. SID's, Star's and route set prior to start up in Mancester (EGCC). Didn't touch anything and crashed whilst in cruise. Latest 350 update and always a clean install with Shader Cache files deleted etc. I never have these issues with Fenix!

1781523798.bin LIRNEGCC01.fpl

• Aircraft: A350-900

• Simulator: FS2024

• Navdata Method: NAVIGRAPH

• WASM Error:

  WASM: Error during HUD_gauge_update execution. Error code : 0xc000001d

  WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm Gauge: EFIS

• Specs: 7800X3D, RTX 5070TI, 64gb DDR5 RAM

• Autosave File:  N/A

On the ground, while manually inserting a fix.

Edited Sunday at 11:23 AM2 days by Tommius84

6 hours ago, Tommius84 said:

• Aircraft: A350-900

• Simulator: FS2024

• Navdata Method: NAVIGRAPH

• WASM Error:

  WASM: Error during HUD_gauge_update execution. Error code : 0xc000001d

  WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm Gauge: EFIS

• Specs: 7800X3D, RTX 5070TI, 64gb DDR5 RAM

• Autosave File:  N/A

On the ground, while manually inserting a fix.

Same here.....

Wasn't able to do this this morning as I was walking out the door for work but had 1 freeze and then a wasm crash. Sunday night, flight from VHHH-KATL, 10 hours in and then everything freezes, plane starts flying to northern Canada. I delete the wasm folder, reinstall the aircraft, and then start another flight last night at 2300. Woke up to see that the aircraft isn't moving. Before I walk out the door, I see the orange screens of death. Each display with its own associated code (pfd, mfd, etc...). Idk what else is going on here, I'll try again tonight. Despite this two events, I was able to do long haul flights with no issues for 15 days straight.

Aircraft: A350-1000

Simulator: FS2024

Navdata Method: NAVIGRAPH

Specs: RTX 5070, 32gb DDR5 RAM

Autosave File: N/A

• Aircraft: A350-900 Nocabin v1.2.6

• Simulator: FS2024 SU5.1

• Navdata Method: NAVIGRAPH

• OFP: Not created or uploaded at this early stage

• WASM Error: Error FCU WASM crash info displayed. Only FCU panel was orange.

• Specs: i5-12600K, RTX 4070 Super, 12Gb VRAM , 32Gb RAM, Windows 11 Professional

• Autosave File:  N/A
  
  Initial observation:
  First WASM crash observed with A350. Loaded sim, selected Free Flight then selected LEBL, Gate 217 (MK Studios scenery). No destination airport selected. Everything OK. Selected End Flight then selected EGCC, Gate 12 (Inibuilds scenery) as departure with no destination airport selected. Went into cockpit. Only FCU WASM crash observed. Other gauges all OK.
  
  Next steps:

• Exited sim. Restarted sim and selected EGCC, Gate 12 once more. No WASM crash.

Console log.txt

I know this is a wild thought but I think everyone has used the navigraph charts and had WASM issues. I guess my question would be...Does anyone have the same issues using the LIDO charts?