WASM Crash Report SU3 V.1.1.4

[CptFerox]

Happend on my overnight flight from Doha to Auckland. About 5-6 hours into the flight, when i woke up in the morning the airplane was still flying but all screens/knobs except for the OIS were unresponsive.

 

• Aircraft: A350-1000
• Simulator: FS2024
• Navdata Method:  NAVIGRAPH
• OFP: look at PDF
• WASM: Error during EFIS_gauge_update execution. Error code: 0xc0000005
• Specs: 13900k, RTX 5090, 64GB DDR 5 GSkill
• Autosave File:  unfortunately had autosave disabled on this flight

OTHHNZAA_PDF_1756073003.pdf

[CptFerox]

 

Edited August 25 by CptFerox

[Ron311280]

Had the same problem on my last Flight. 

[Eddie]

Hello,

Thank you for the report! Very sorry that you experienced this crash. It is very much worth it to keep autosave going in the background as it not only beneficial for you, but for us also as it helps identify WASM crashes a lot easier. 

I've forwarded your information to the team regardless.
Thank you 🙂

[CptFerox]

Hi @Eddie,

Did the same flight yesterday. Had the same behaviour about 7:30 hours into the flight. I was way off course with no buttons/knobs working except the OIS. Unfortunately this time there was no WASM Error to be found. I had autosave enabled this time though and wanted to provide you with the file.

 

1756618484.bin

OTHHNZAA_PDF_1756586787.pdf

Edited August 31 by CptFerox

[Eddie]

Hi there,

Thank you for the follow-up. We'll take a look! 
Did you try loading in using the autosave? It's a quite a neat feature. 

[ZestyDog69]

This happened to me too moments ago, it is very sad, but I will try out this autosave feature.

 

[ZestyDog69]

Thanks the autosave worked great!

 

[Eddie]

3 minutes ago, ZestyDog69 said:

Thanks the autosave worked great!

 

Awesome! Also something to keep in mind, incase autosave didn't properly load, try a second time and always from a runway. Sometimes first load of the save may not initialise properly; a second one usually does the trick.

Thank you 🙂 

[CptFerox]

14 hours ago, Eddie said:

Hi there,

Thank you for the follow-up. We'll take a look! 
Did you try loading in using the autosave? It's a quite a neat feature. 

yup. was able to continue my flight and had an awesome approach into Auckland 

[Ulvar50]

• Aircraft: A350-900
• Simulator: FS2024
• Navdata Method: NAVIGRAPH (latest)
• Specs: Intel i9-11900k, 64gb, AMD RX 7800 XT

[noolaero-vdgs-esms.wasm]  Sim | EXCEPTION 25: The AI operation requested cannot be completed
[noolaero-vdgs-eidw.wasm] [noolaero-vdgs-eidw] EXCEPTION 25: The AI operation requested cannot be completed
[noolaero-vdgs-esgg.wasm]  Sim | EXCEPTION 25: The AI operation requested cannot be completed
[noolaero-vdgs-essa.wasm]  Sim | EXCEPTION 25: The AI operation requested cannot be completed
[inibuilds-A350.wasm] Error: Unable to open directory 
[inibuilds-A350.wasm] \work\autosaves\
[inibuilds-A350.wasm] 

WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005
WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty
 

Edited September 3 by Ulvar50