WASM crash reason?

[AntonyCh]

I think it may be probably related to data between msfs and navigraph. Most reports i seen are using navigraph. And I also encounter the first time WASM crash after I subscribing navigraph and using it as navadata method. Before subscription, I never encounter any WASM crash in A350, even after 1.2.1 update. So I hope dev try to figure out whether this point is the problem.

Edited March 2 by AntonyCh

[Lukasz Krajnik]

Interesting. Since I switched navigation source to Flight Simulator I have not experienced any WASM crash. 
I still have Navigraph subscription activated, AIRAC updated from Navigraph in FS2024 and A350, and all functions related to Navigraph are available in A350. 
Not sure if this is relevant but that's my observation.

Edited Friday at 04:54 PM by Lukasz Krajnik

[leo5now]

Helloo! So I commented in another topic in the forum how I was done with the A350 and can't be bothered to find the issue, however that was when I decided to take on it one more time but in SU5. 

What I found is that changing the navdata for me personally does not work, but not downloading the terrain data helped fix it. Right now, as I am typing this, I am doing a stress test on the A350. Normally it WASMS around 45 mins - 3 hrs into the flight, but it's still going for over 16hrs now since im doing SIA's longest flight JFK-SIN. I still need to test some more if SU5 actually fixes it, but I will report back if it is actually the terrain radar. Also, using charts and the ANF just works fine, and im using Navigraph as my navdata.