WASM Crash

[Avia]

I was making myself some sausage and fries when I looked over at my navigraph seeing I was deviating from my flight route. When I rushed back to the flight deck I noticed I could not press anything, everything was frozen, but the plane was moving. Rest in piece 5 hours.

About 20 minutes prior to the crash I was looking through all the ECAMS getting familiar with the aircraft and how the systems and buttons work. I didn't really press anything out of the ordinary.

• Aircraft: A350-900
• Simulator: FS2024
• Navdata Method: NAVIGRAPH
• OFP: Not sure if it's related but sure LFBOOTHH_PDF_1740685756.pdf
• WASM Error: WASM: Error during CTR_gauge_draw 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
• Specs: i7-11700f, RTX 3050 and 36 GB RAM

Edited February 28 by Avia

[Hans-Peter Benz]

Exact same problem, already occurred after 17min in flight. 
checked the COND Ecam Page, afterthis systems frozen, can’t change anything. Plane still flying, but not controllable anymore.

[Avia]

3 hours ago, Hans-Peter Benz said:

Exact same problem, already occurred after 17min in flight. 
checked the COND Ecam Page, afterthis systems frozen, can’t change anything. Plane still flying, but not controllable anymore.

I was on the COND page at one point too, probably right before i left the flight deck. This might be where the WASM crash comes from👍🏻 

[David Grundstrom]

I had this issue twice in the last two flights, yet there was nothing in common as far as what caused it. One was in flight while using SEC Flight plan, another was on the ground having used the Notepad after receiving clearance. PMDG has had these crashes too, yet they solved them. Can Inibuilds do that too? I'm losing interest fast here, I have no desire to start a 7 hour flight only for it to crash 3 hours in.

Edited February 28 by David Grundstrom