Sure however I would trust Asobo to look after their own disposals but certainly not 3rd party installs, that’s just asking too much.
There is a link in the content.xml file that tells MSFS where its nav data is located.
In the case of Navigraph (specifically), it does not use the registry, but when you install their MSFS nav data using their data manager, it changes the link in content.xml to point to the Navigraph folder in Community.
If you subsequently simply remove Navigraph from the Community folder, the link in content.xml now points at nothing - which is why the sim will load with no nav data at all.
If you uninstall Navigraph using the data manager program, it will remove the Navigraph folder from Community and reset the link in content.xml back to the MSFS default nav data.
Probably a good rule of thumb would be: if you installed an add-on by simply dropping a folder into community, it would probably be perfectly save to simply move or delete that folder later. This would apply to most of the freeware airports at flightsim.to, the WT mods, etc.
On the other hand, if you installed an add-on into Community using a dedicated installer, it is probably best to remove them using the corresponding uninstaller. This would apply to many payware airports or aircraft.
2 Likes
Totally agree, just wanted to hint that in case of some addons/mods removing and later adding it from/to the Community folder not necessarily results in an entirely “clean” version of it.
State saving is a feature and especially aircraft addons use it quite regularly (even if it’s just the hobbs meter).
Anyway, for Navigraph that’s a different story as you described and the rule to use the installer/uninstaller if there is one is the best way to not run into issues.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.