[[v1.0.2] WASM Crash after loading up]

• Aircraft: A350-900
• Simulator: FS2020
• Navdata Method: SIM DEFAULT
• OFP: Not needed, did not happen during a flight-plan/route procedure event
• WASM Error: WASM: Exception c0000005 in gauge Systems in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm
• Specs: 
  • i7-7700k
  • GeForce GTX1660SUPER
  • 4x 8GB GSkill Trident Z
• Reproduce:
  • So prior to this, I deleted the contents of the WASM folder as described herein the forums. I then updated to 1.0.2 using iniManager
  • I then loaded up into a default WSSS with the Singapore Airlines livery.
  • After waiting 12 minutes (as is normal after loading up the aircraft after deleting WASM folder contents), I spawned in. I clicked Ready to Fly
  • Then I noticed nothing came alive after turning on batteries, and the External Power.
  • I then suspected a WASM crash, opened the logs, here we are.

[Everthing freezes after making changes in FMS]

Out of the 5 attempted flights I've done in the A350, haven't landed it once. I fly on VATSIM which requires constant tinkering of the FPLN page whether altitude/speed restriction due to a new altitude restriction or a runway change.

And out of those 5 flights. 4 of those were before takeoff/during taxi, it was due to a runway change on the ground that required me to tinker with the FMS. The furthest I've gone is a flight at top of climb, then a WASM crash/freeze

[[1.0.1] FS2020 WASM Crash when sending revised T/O speeds from OIS via "SEND TO FMS" function]

• Aircraft: A350-900
• Simulator: FS2020
• Navdata Method: SIM DEFAULT
• OFP: (Attached)
• WASM Error: WASM Error: WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm
• Specs: i7-7700k // TUFGaming 1660Super // 4x 8GB GSkill TridentZ
• Other Notes: 
  • First [attempted] flight on 1.0.1. Prior to this, I updated via iniManager, and deleted WASM folder. I then loaded up aircraft for first time, which took 15 minutes. After that, because I spawned on another aircraft on VATSIM, I exited to main menu, then respawned at another gate, loading time around 2 minutes.
  • I got the WASM Error, but for some reason it doesn't show in the video or the screenshot I took. I did manage to get the WASM Error.
• Steps: After a runway change and swap from SEC F-PLN to SWAP to ACTIVE, I ran a quick recalculation of the T/O speeds on the OIS display, and clicked "SEND TO FMS". When I did, all displays froze.
• Screenshots / Videos
  • Video: Skip to 37:25

WSSSWMKK_PDF_1740840855.pdf

[WASM crash after entering FIX INFO]

Had the exact same WASM error as above. However, this was when I clicked on the TMPY INSERT (Because I had deleted a FPLN DISCON): WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm

 

• Aircraft: A350-900
• Simulator: FS2020
• Navdata Method: NAVIGRAPH
• OFP: WSSSWMKK_PDF_1740666897.pdf
• WASM Error: WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm
• Specs:
  • i7-7700k
  • ASUS TUF Gaming GeForce GTX1660SUPER
  • 4x 8GB GSkill TridentZ RAM
• Screenshots/Videos
  • SCREENSHOT: 1x Screenshot of WASM and MFD below. Entry of 23:56:20. (There was a separate occurence that wasn't documented, WASM log 22:35:24. Same message except it was now in "Systems" instead of "MFD". Turning on the batteries did not elicit a response. Since it happened during my initial spawn at the gate, I just restarted the flight.)
  • VIDEO: I was also doing a test stream/recording. Click me for the video, it happens at approximately 01:06:00 (bookmarked). Notice that all the screens freeze but the aircraft was still flyable, at least with the stick. I did not dare touch the thrust levers or anything anymore. 
    • I was doing the Arrival Preparation into WMKK. I deleted a FPLN DISCON. As I was about to TMPY INSERT, everything froze up.
  • Unfortunately no steps yet to reproduce as I did this flight in the evening before going to sleep, so now a bit tired to do the whole flight again . If I do another flight, I'll record it again.
  • Unfortunately I also had an undocumented occurrence the night before, but it was inserting the approach transition into WMKK ILS32L, on the MFD.