WASM Crash Report

[benlong]

Hi,

 

• Aircraft: A350-900
• Simulator: MSFS24
• Navdata Method: Occurs with SIM DEFAULT and NAVIGRAPH
• OFP: N/A
• WASM Error: WASM: Varget of NONE in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm failed with error 0x00000004
• Specs: AMD 5 5600X, Nvidia RTX 3060, 32GB DDR4 3600MHz RAM

No autosave folder could be found in the Work folder.

Details

When spawning on any airport at Fiji, regardless of scenery installed, the above WASM issue occurs. If performance mode is ON, the NLG is invisible. If automatic cover removal is ON, the covers are not automatically removed. The aircraft does not work, screens do not turn on and GPU is unable to be used, regardless of how much time is elapsed.

Actions taken without success: cleared community folder, cleared WASM folder (WASM issue reoccurs each time you try and respawn in and around NFFN), cleared scenery index, changed liveries, removed all liveries, reinstalled aircraft, disabled Oceania World Update, disabled photogrammetry, changed default panel state, turned performance mode back to ON, restarted flight, removed Navigraph and associated navdata, removed all GSX profiles.

The aircraft has no issues at any other airport, that I have experienced. Interestingly, the issue occurs not just at NFFN (also occurs at other airports around Fiji) and happens irrespective of whether scenery is installed or if the World Update is used.

Regards,

Ben

[Eddie]

Hello Ben,

Thank you very much for the report. Apologies for the inconvenience. We'll take a look!

[benlong]

18 hours ago, Eddie said:

Hello Ben,

Thank you very much for the report. Apologies for the inconvenience. We'll take a look!

I've managed to resolve this for now. I removed the SU2 beta, launched into the aircraft (with a fresh WASM folder) in SU1 which then had no issues, so I reinstalled the SU2 beta, and the issue has gone away.

 

UPDATE:
Now the aircraft has bricked again and the issue has returned no matter how many times I delete and reinstall the SU2 beta. I've had some friends report having the same issue. Looks like the aircraft is unusable at Nadi for now.

 

Edited Thursday at 03:17 AM by benlong

[Eddie]

I've tried multiple times not to reproduce this and still no avail. Truly frustrating on both parts. Either way, I've let our system guys know and well try our best to reproduce this. 

Thank you