Please only mention one issue per topic so that others can easily see what has been reported
What I expected to happen.
Clarify your expectations. It’s easier to understand the anticipated
behavior and determine whether it’s truly a bug or a usability issue that
needs to be reviewed.
What actually happened
I am experiencing a repeatable failure in the Aerosoft CRJ V2 in MSFS 2020 when using Navigraph Charts in the CRJ EFB.
System/setup:
● MSFS 2020 Steam
● Aerosoft CRJ V2 2.1.10, purchased/installed through Aerosoft One
● Navigraph subscription/current AIRAC
● Navigraph Hub with Aerosoft CRJ V2 package installed
● Windows PC with RTX 5080
● Quest 3/Virtual Desktop VR
The CRJ and Navigraph EFB integration had been working normally for a long time. This problem appeared suddenly.
Reproducible behavior:
I can load my departure airport charts normally in the CRJ EFB. When I back out of those charts and attempt to select/open a chart for the destination airport, the CRJ experiences what appears to be a WASM failure.
MSFS itself continues running and the aircraft continues flying, but the CRJ cockpit becomes unresponsive: gauges/displays stop updating and cockpit controls, including the throttles, stop responding.
Initially I experienced this twice flying KABY–KATL at approximately the same point in the flight. I then tested KMGM–KATL, a route on which I had not previously experienced the problem. The same failure occurred when I attempted to switch from the Montgomery charts to the Atlanta charts.
I subsequently reproduced the failure while sitting at the gate, so it does not appear related to aircraft location, altitude, scenery load, or overall PC performance.
Troubleshooting already performed:
● Verified CRJ V2 is current at version 2.1.10.
● Deleted the CRJ compiled WASM cache and allowed MSFS to rebuild it completely. Failure remained.
● Completely uninstalled and freshly reinstalled CRJ V2 through Aerosoft One. Failure remained.
● Removed the Aerosoft CRJ V2 navigation-data package through Navigraph Hub and tested again.
● With that package removed, chart behavior changed somewhat: chart lists could appear but some actual charts were blank, and the EFB/aircraft still became corrupted/unresponsive.
● Reinstalled the Aerosoft CRJ V2 package through Navigraph Hub, restoring the system to its normal configuration.
● After restoring the Navigraph CRJ package, I can again reproduce the complete cockpit/WASM failure while sitting at the gate simply by navigating between airports/charts in the CRJ EFB.
The departure-airport charts can initially display normally. The failure occurs when navigating away from them and attempting to retrieve/display charts for another airport.
Because this behavior has survived a complete CRJ reinstall and WASM rebuild, and because it is specifically triggered by interaction with Navigraph Charts, I wanted to report it here as well as to Aerosoft.
I would be happy to perform a specific reproduction sequence or provide additional information/logs if Navigraph or Aerosoft would like them.
Thank you.