Inibuilds A340 Master WASM Crash Thread v1.0.9

[IniJamir]

This thread will be the new location for all WASM Crashes relating to the Inibuilds A340 for Microsoft Flight Simulator 2024.

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

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 A340 v1.0.9 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 messages that do not follow this formatting are subject to deletion.

Thank you.

[Michael G]

Hi, I loaded up the sim today and updated to this latest version. Afterwards I loaded into HKJK stand 11 and powered on with the battery then the gpu. After a few minutes I turned ADIRS to NAV and went to the EFB to login to navigraph and then downloaded the latest AIRAC. Almost immediately after I got the WASM crash.

[Coherent GT] Failed to locate file vfs:///html_ui/global/undefined

Invalid script (command not found - perhaps a space is missing or there's an extra space?): "="

[inibuilds-A340.wasm] Error: Unable to open directory 

[inibuilds-A340.wasm] \work\autosaves\

[inibuilds-A340.wasm] 

WASM: Error during Event NavigraphUpdateCompleted called execution. Error code : 0xc0000005

WASM: Module vfs://inibuilds-aircraft-a340/SimObjects/Airplanes/inibuilds-a340/attachments/inibuilds/Function_A343_Interior/panel/inibuilds-A340.wasm is now dirty

[HURTFULD3IK]

nearly the same problem, but now i cannot use any Inibuilds airplane cause every ini plane has that red wasm module crash on boot, and i tried everything, believe me...

[Sleeveless]

A340 VIP EIS2 (Has happened for EIS1 as well for me- check discord- sleeveless)

MSFS 2024

iniManager

Navigraph

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

WASM: Module vfs://inibuilds-aircraft-a340/SimObjects/Airplanes/inibuilds-a340/attachments/inibuilds/Function_A343_Interior/panel/inibuilds-A340.wasm is now dirty

5800x, 6950xt, 32gb ram 

 

Happens with very busy airspace on the Vatsim network) I went to go direct a waypoint that said was not in the system (JYLET) which the correct spelling is (GYLET). Once saying the way point didnt exist, I clicked on my airport to change my arrival to get the correct waypoint and thats when she crashed.

 

 

1770498458.bin AsoboReport-RunningSession.txt KPHLKSJC_PDF_1770494953.pdf

Edited February 8 by Sleeveless

[Sleeveless]

And another one. I can duplicate it. I'm having the issue more on EIS2 however same concept. Changing arrival  airport runway will almost certainly crash the wasm. This was pax eis2. I can give the bin if requested however either it's not a priority or you may already know the issue and not know how to fix it because it appears the 350 has the same issue and it appears to be nothing but silence about it.