I got an official reply on a zendesk ticket that Navigraph (and several other tools/addons like OnAir) can be the cause of the Out-of-Nowhere-CTDs in MSFS. Is there any experience with Navigraph being the real cause of it, anyone of you having problems (and if yes, how did you solve them)?
Not that I paid around 100 Euros for the yearly subscription for it… grml…
Thanks
It’s a difficult question to answer. Simply because everyone has a different configuration with their PCs. Just because a Navigraph installation caused CTD on one computer, doesn’t mean it’ll cause CTD in another computer. The same thing applies the other way around.
The better question is. Are you having CTD issue because you have Navigraph installed. If so, did you eliminate the CTD by uninstalling Navigraph?
What about having Navigraph incompatible with another addon, that maybe Navigraph itself doesn’t have an issue, but when it’s paired by something else that can cause the CTD.
I mean when its officially listed in a support-answer like “The following addons are causing problems” they must have at least a small idea of what is causing the problems.
I personally dont have any other addons. But even without I face the one or other CTD so I am still trying to chase down the problem (which is easier in X-Plane since we have a logfile giving us some more information than an event-id 1000).
I’ve been using Navigraph for a long time and use it to display charts on a second monitor as well as the live position of the plane in the sim; it’s crashed randomly both with it on and with it off, so I think the Zens are just looking for something to blame
I too use Navigraph, and haven’t had an inflight crash in weeks, nearly a month I expect.
I too use Navigragh but can not tell you if it is or is not the cause of some of the CTD I’ve experience.
I do use Navigraph, LittleNavMap, Touchportal, Mobiflight, an Excelsheet, Firefox, Thunderbird and OBS parallel and don‘t have CTDs. Not with standard Aircrafts nor with the FBW
So, the answer should be no and yes……That means, Navigraph is not necessarily a factor of CTDs.
It’s a hard question to answer for any add-on without proper logging in place.
Some add-ons/mods can potentially cause a CTD if they are not kept updated.
As for Navigraph, I’ve heard some users that removed it incorrectly experienced issues.
I’ve been using Navigraph myself without any problems, so I reckon it would only be a problem in very specific cases such as the scenario I mentioned above.
No crashes ever with Navigraph for me. I have all the apps except Charts in game Panel.
If you simply delete/move the folder out of Community the sim will experience issues as it has no nav data any more. The Navigraph app, whose name escapes me, will remote the data correctly. The other things you can do are either hand edit the content.xml file, or delete the Navirgraph line in it, then relaunch the sim.
I don’t use it and still get random CTDs. I was thinking nvidia driver
A great and simple example of why it can be so hard to track down and fix CTDs!
More an example how not to handle customer support by throwing some testballoons towards the customer without providing evidence.
Honestly - we get a list of addons that can cause trouble, we disable/remove all the addons: Still trouble. And blaming a dozen of addon-devs for it.
Doesnt look too professional to me, to be honest.
I use Navigraph Charts in VR on every flight.
No CTD since WU6 (I fly daily)
You’re kidding right?
I too have used Navigraph, for about 6 months,
I have very few CTDs, but when I do, I analyses them, to find out what/were they occurred, and in no case,. was a CTD (for me) caused by Navigraph
Addons are always blamed for CTDs, but that cannot be true in ALL cases, as X-Box is know to CTD !!
Hi,
please can you forward me (via PM) the answer from your Zendesk ticket? We have no information about CTDs since months. Not from enduser nor have we gotten any info from ASOBO/MS.
When they say, CTDs are possible with addons then I guess,they know why and what we can do against this CTDs. We would fix this CTDs when we know what happened, but without any logging it’s not so simple … but it looks ASOBO/MS has an idea from where are the CTDs are … and what the reasons are.
Thank you
Richard
Richard, you might hope so, but it certainly does not look like it.
I have no problems to make this public (also for the other devs that may be affected):
*snip
Thank you for sending in that file. I can see MSFS2020 is crashing due to a general fault:
Name des fehlerhaften Moduls: FlightSimulator.exe
These errors can be caused by numerous reasons.
Using mods (including liveries) - especially after a sim update
Overclocking your CPU/GPU/RAM – revert to default clock speeds and test
Using third party applications that cause conflict (make sure ALL third party programs being used with MSFS2020 are updated to their latest versions). If you are using third party programs (FSUIPC7, NeoFLY. Little NavMap. etc.), test by starting with one, then add others to try and isolate if there is an issue.
Make sure all software and drivers for peripherals are up to date (flight stick, throttle, rudders, etc.)
Note - after sim update 5 we are also noticing DLC purchased from the in game marketplace and elsewhere can cause this type of crash as well. Remove any DLC and test by adding them back in one by one.
Safe Mode doesn’t deactivate plug-ins and software additions that allow for the customization or add new functions to Microsoft Flight Simulator.
If the sim keeps crashing in Safe Mode uninstall freeware and payware plugged into the base sim and/or the peripherals you use to play Microsoft Flight Simulator, then try again.
Examples of popular plug-ins/software
Navigraph (use NavData Nav Center to remove the Navigraph database)
OnAir
Liveries Manager
FSEconomy
Self Loading Cargo
ATC Renamer
Splashtop
Pilot Path Recorder
Weather Force
ModManagerX
*snap