After some testing, I’ve noticed that the ini/MS A330-300 reverts to a WASM crash state whenever I select the ANOVP2A Arrival regardless of transition.
Here’s the route I am trying: NZAA/05R ANVAR2Q IGBAT H384 NP H252 NS Y288 IPRAK ANVOP2A NZCH/02
Is anyone else experiencing WASM crashes with this arrival only? I’m suspecting its a database issue since this is the only arrival it happens with.
I’m using the latest AIRAC via the Navigraph HUB application.
Thanks so much for your response! It’s much appreciated.
The issue is with the STAR (AVNO2A) - both I and a colleague tried it on two different systems with the ini A330-300 (RR), which resulted in a WASM crash. The other STARs paired with the ILS02 worked fine. We then tried it with different addons (PMDG T7 and Fenix A320) and both were able to load the STAR without a WASM issue. Both simulators (FS24) had the latest Navigraph AIRAC installed into the sim.
Hi,
Please report this to Inibuilds; it appears to be an isolated issue on their aircraft.
Reason for my assumption:
All stock aircraft (which are included in the MSFS 2020/24) use the in-game data (BGL data). So, there is no separate/own dataset (like for PMDG, Fenix, …) - the same data is used for the ASOBO B737Max, for the C172 with the G1000, for the TBM and the G3000, …
So, when this should really a data issue we would expect this crash everywhere, in every aircraft which uses this in-game data, but that is not the case here. When you enter this arrival in the example, the Garmin G1000, you will see that the procedure works correctly without crashing.
So, the only difference is the WASM between, and that is what we can´t control.
You can do the test on your own:
Try to enter the procedure, i.e., in any stock aircraft (but not in Inibuild aircraft), and you will see the same effect: the procedure can be loaded without any issue or crash.
Here from the G1000 with the latest in-game (MSFS2024) AIRAC 2603 installed: