After update of msfs, i have a crash and back desk. I find that is the file " layout.json" in navigraph-navdata which is responsible. I d’ont know what can I do. Can you help me.
Sincerly
Hi,
And welcome to Navigraph. How have you detected that this file is the culprit? Why do you mean that this file is the reason? Or better yet, how did you identify it?
Cheers,
Richard
by elimination, I emptied the community folder and reintroduced the folders one by one by relaunching msfs each time, moving the files and reintroducing them one by one, this is how I found the file at fault
When does the sim crashed? During the startup process, during a flight or when you click something in the sim? Where and when?
I ask because this file is a simple text/JSON file, which contains only files, and this file will not be used directly from the sim. So it´s very unlikely that this file results in a crash.
Cheers,
Richard
good morning, I’m testing FS2020 with the different add ons, it seems that the problem is related to the AIRAC installed inside FS2020 itself, because if I start the simulator with the updated AIRAC of the various planes, but not those of FS2020, no CTD occurs. I tested with 320 Fenix and with PMDG
Hi,
And welcome to Navigraph …
Yesterday, ASOBO/MS released an update that contained the wrong package. This package results in a CTD during the MSFS startup process. This is not what we can handle, but there is a temporary fix to solve this issue, and you still can use our data:
You can find the steps here:
I hope that helps,
Richard
Had the same problem and I can confirm that your temporaryy solution, to delete “BUSH TRIP - SCOTLAND” solved the problem.
Thanks a lot for this solution !
The problem now, will be that we will probably never know easily if and when Asobo will correct this bush trip module.
We opened a ticket in their developer forum. I hope we get an answer to this issue.
Our main question is how we can avoid this in the future because this is not really funny for everyone, for you as a customer/user, and not for us. But I guess, for that, we need ASOBO/MS …
Thanks for your confirmation - much appreciated…
Cheers,
Richard
How can a bush trip package conflict with Navigraph, in the name of God? That is the answer I would like to hear.
Probably a corrupt airport package in that bush trip which conflicts with Navigraph data?
It´s an excellent question, but I´m unsure if we ever get an answer. After a few hours of analysis, I guess it´s not the bush trip package per se because it wasn´t updated due to the AA03 yesterday. It´s the same as before the update.
I assume that something went wrong with deleting the WorldHub airports. They lost property any reference to precisely this package, but we still have this reference in our data and therefore bum …
But again, all these things are speculations. I´m pretty sure they will fix it, but they will not tell us the exact reason. We will see; I hope I am wrong.
… back to the origin topic of this thread, please 
Cheers,
Richard
This is the most significant part of this topic. I am a developer, and I hate companies that break and fix APIs or SDKs without telling me. If that happens, the software I will write will be pulled together with duct tape and best wishes.
Exact the same thing happened to me today. Eliminating navigraph-assoziated items in the communitiy folder solved the issue so far; meaning no CTD on MSFS-Startup.
Best regards,
Matthias
Matthias,
First of all, welcome to Navigraph - you may not uninstall our Navigraph navdata package. It´s a confirmed bug from ASOBO/MS. They are working on a fix to solve the problem.
When you follow these steps, you can use our data as in the past with the current MSFS version, too:
Hope that helps,
Richard
1 Like
Hotfix Deployed.
1 Like
The hotfix solves the issue even when you have installed the full WU17 plus the bush-trip package. Thanks, @Casualclick, for your support and help, and thank you very much to MSFS for their fast fix.
Cheers,
Richard
Ok, they uploaded a fix including new navdata. Does that mean we can go back using navigraph navdata again or to leave as it is for the moment?
It was not necessary to remove our package (as you can read in the posting of the link). But when you have removed it, you can now re-install it again … All is working as for 48 hours - no CTD any longer.
MSFS has fixed their bug with this hotfix.
Cheers
Richard
1 Like
Hi and cheers from Germany. I did all the suggested steps, deleted the navigraph data from the community folder, even deleted the hub, but still CTD after trying to start MSFS2000. Any tips what to do?
I use ProSim, FlyElise and MSFS.
I could start MSFS once without starting anything else, and could install the hotfix. But after a new start CTD all the time
Hi,
Welcome to Navigraph. Unfortunately, this is more of a question for the MSFS forum.
Sorry, but this is not the proper forum for such support questions. The MSFS forum has many helpful users and also a group of community managers who can possibly help you find the reason for your CTDs.
This topic handles the bug from the AAU3, which was fixed with the hotfix rolled out today.
Cheers,
Richard