In my case (PC Windows 11 Airbus A320neo V2), Simbrief still causes my MSFS2020 to Crash to Desktop after flying for about 20 minutes.
I have had to uninstall the latest AIRAC cycle (October 2).
Anyone else?
Hi…,
What makes you think SimBrief is causing a CTD? Do you mean Simlink?
Regarding AIRAC updates, MSFS released a solution to their issue at AAU3 and Navigraph crash MSFS - #69 by NAVData.
Cheers
ian
Hello Ian,
I think that you misunderstand me.
I did follow the MSFS solution at AAU3 et. etc., but in spite of that I still got a CTD after some 10minutes of flying my Airbus A320neo V2.
That was in my case solved by uninstalling the AIRAC Cycle.
Cheers,
Claus
The A320neo V2 did get a major rework of its LNAV code with AAU3. It’s most likely just a different crash caused by a different part of the same large MSFS update.
Navigraph does not develop the A320neo V2 and despite making the data, will not be able to investigate the issue on their own.
So what you need to do is to submit a bug report to Microsoft/Asobo who will be (through iniBuilds) the only ones able to determine what in the data is making the A320 crash.
If there is an issue with the data, they will be able to reach out to Navigraph and explain what the issue is, at which point Navigraph can issue a fix for their data. It’s also possible the data is fine and there is simply an unexpected bug in the A320 which can be fixed without amending the data.
Regards,
Tim
Hi Claus,
The hotfix for AAU3 from MSFS is working as expected. They fixed this, but it had nothing to do with our data. Therefore, it´s very unlikely that your CTD has something to do with the AIRAC cycle, even when it looks so to you.
I will try to explain why I think that you must have any other issue:
The navigational data will be loaded during the startup of the MSFS, which means when there is any issue (in the sim or in the data itself), you will immediately see this as a CTD - what was the case after the update before MS fixed this internal issue?
Now, you wrote that this happened during a flight after a specific time. Such CTDs are very difficult to find; it could be memory issues, heat issues, a graphic card driver issue, a calculation error somewhere in the aircraft, faulty packages that are not 100% compatible with this sim version, or something else, but it´s normally not the data.
But I assume it´s reproducible when you wrote it´s solved when you uninstall the cycle; therefore, we can try reproducing your CTD.
Can you explain in detail:
- the flight plan,
- where this exactly happens (altitude, position)
- if you have any other packages in the community folder, excluding our navdata package
With such information, we should reproduce your CTD and can analyze why this happened.
Thank you very much for the additional information and your effort in this.
Cheers,
Richard
PS: I have moved your topic into the correct category, and I have also changed the title to avoid misunderstanding … because Simbrief can´t cause a CTD in MSFS as you have written in your initial posting 
Rodeo314 has the answer,
Thank you!
That being said, Richard’s post contains excellent advice about what data you should provide in the bug report, regardless of whether you submit it to Microsoft, Navigraph, or both. And his post indicates Navigraph is willing to investigate so you might as well report it here as well (IMO, preferably in a new, dedicated topic this actually already is a dedicated topic, my bad).
Regards,
Tim
1 Like