Jump to content

WASM Crash: LAX-BNE - Crash when selecting runway and approach type


Recommended Posts

Posted

Example WASM Crash Report

Flying on the most recent AIRAC (2505) when flying LAX > BNA I had already reloaded the flight for a CTD early (about an hour and a half) into the flight. The flight recovered fine so I continued. However, some issues did creep up:

* I was no longer able to load any fixes on the FIX INFO page. I could enter info into there, but nothing would appear on the ND nor the MCDU. Prior to the sim crashing, I had utilized all 4 FIX pages with pilot defined waypoints. About 8 hours later, I was loading my approach data into BNE, and I realized that even though the runways popped up on the data page, no approaches nor STARS were available. When I selected RWY 19L, it did allow me to move on to the next box, but nothing was actually entered in the MCDU approach page, it kept just giving me blank data.

I did get the option to INSERT, so I did, clicked YBBN again, selected rwy 19L again, then WASM crashed.

 

To reproduce

  • Load autosave
  • Select any approach runway into BNE.
  • Select any approach type (i only had 1 available, just said 19L)
  • Insert with no STAR
  • Go back to select any approach type
  • Select rwy 19L

Information

  • Aircraft: A350-900
  • Simulator: FS24
  • Navdata Method: NAVIGRAPH - 2505
  • OFP: Attached
  • Specs: Ryzen 9800X3D, RTX 5080, 64GB RAM
  • Autosave: Last two autosaves attached - pretty sure the newest saved after the crash
  • WASM: Error during BAT_gauge_update execution. Error code : 0xc000001d

FlightSimulator2024_12KEobEyAs.jpg

KLAXYBBN_PDF_1746957875.pdf 1747004102.bin 1747004344.bin

Posted

A similar example last night. A359 (no cabin) in 2024. Gate 304 at Aerosoft' s EBBR. Followed normal pre-flight and problem came when entering the arrival, actually it was the transition that caused the issue.

Route: EBBR/07R HELE3V HELEN L179 COA L608 SUMUM Y6 TOSVA TOSV1A EGSS/ABBOT.I04

As soon as I selected the ABBOT transition, the FMS just stopped responding - re-started the sim and had exactly the same issue again.

Using Navigraph data/charts and imported the basic route from Simbrief. 

In both cases, these were flights started from scratch, not recovered Autosaves.

Having had engine one randomly at 1,499C earlier this was not a good experience with this plane. Please resolve. Like many people, I have a limited time to spend on flightsim and faffing around like this is not what I expect from software at this price point.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...