Roders

Yeah my WASM crashes were happening c. 30-60 mins after departure, so a bit earlier, but also only with latest Navigraph AIRAC. Might be worth changing the title of this topic to better reflect the Navdata issue. Hoepfully ini see this. Because its a market place release, update could take weeks or even months - might have to shelf this aircraft as flying on Vatsim without updated AIRAC data is a bit tricky. Shame as the A343 is by far my favourite AC out there.

@iniBuilds I just tested the exact same flight with default sim navdata and there were no issues - to double check I ended the flight and restarted it with updated Navigraph Airac data and the BAM, the same WASM errors and issues. I confirmd in another thread that other users with this problem are experiencing the same behavior. I am renaming the title of this thread accordingly.

I am having the same issue, however I realised that the only flight I was able to complete was my first flight when I forgot to download updated Airac. @Mantock @Freitas138 @pappa_razzi @Jure are all of you flying with Navigraph AIRAC installed? Try with default sim... I dont have time to check this myself as I already spent my entire weekend trying to sort this out (great use of my time btw thanks iniBuilds).

@aidenbuch Have you managed to complete any flights since? I want to test with default Navdata but I dont have the time - I just spent my entire weekend starting A340 flights that ended up like yours - honestly flight simulation has to be up there as one of the worst hobbies ever, cant think of anything else that consumes so much time yet reaps so little rewards.

@flyaviation @Jesper Persson Any luck in fixing this? I am having the same issue. I opened a new post with console info and logs so will see what ini says.

When the issue happens the waypoint diamonds on the ND are frozen but the actual flight path moves as the aircraft continues flying. Additionally, the chrono clock freezes along with most other flight instruments, strangely the DME values are still updating. The first flight I did in the A340 was Zurich to Tel Aviv - no issues at all. During climb on my last 2 flights (LSZH - FAOR and EGLL - FAOR) I experienced the aforementioned issue. The only thing that stands out to me is that on my first flight I forgot to update the navdata after buying and installing the aircraft... ever since downloading Navigraph AIRAC and importing via the EFB the aircraft instruments have frozen on every flight. Further details below: To reproduce Install aircraft from fresh, wipe the A340 wasm folder Load sim and download terrain data Restart PC and Sim Load sim at any gate/airport, turn auto step climb off, autosave off, pause at TOD off, cabin lights off, auto GPU disconnect on, IRS align time to fast and add some weathering and (this probably makes no difference but to ensure consistency...) Make sure Navigraph navdata is enabled and download the latest AIRAC using EFB Plan/start a flight Around 25-30 mins after departure displays freeze and aircraft becomes unresponsive to manual control inputs Information Aircraft: A340-300 EIS 2 Simulator: FS24 Navdata Method: NAVIGRAPH OFP: Not required, happens on any route. Specs: i7-9700K, RTX 2080, 32GB RAM Autosave: I disabled autosave after experiencing this issue twice before. I also completely reinstalled the aircraft and redownloaded in content manager + deleted the A340 WASM folder to no avail. I therefore do not have access to old .bin files. WASM: [inibuilds-A340.wasm] Error: Unable to open directory [inibuilds-A340.wasm] \work\autosaves\ [inibuilds-A340.wasm] Note: the above errors come up if I search for "WASM" in the console - I have attached the entire console log of errors and warnings. Console.txt

Im experiencing the same issues... Interestingly my aircraft descends and flight controls become unresponsive jsut before reaching cruise.

I noticed this as well, I imagine they are aware but cant hurt to raise the issue here just to be sure 👍