WASM Issues When Using Navigraph Airac Data

[Roders]

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

Edited Sunday at 05:26 PM by Roders

[Roders]

@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. 

Edited Sunday at 01:40 PM by Roders

[Juan Pablo Moreno Saavedra]

Yup, having the same exact issue here, displays, controls freeze and the plane veers off course. Seems a lot of people are encountering this issue. I had no idea it could be connected to the navdata although now that I think about it it seems that the first flight I do when I have forgotten to update navdata it has worked, but when I do after a certain amount of minutes or hours into the flight displays, instruments and controls freeze and the plane veers off course and cannot be controlled. 

[vumi101]

Can confrim as well. Default Navadata no issues. Latest AIRAC through Navigraph gives me WASM crash after about 3 hours of flight.