36 minutes ago, MDFlier said:

What kind of issue do you have that requires the AIRAC to be reloaded? I've never done that (except when the data is updated)

Navigraph’s data manager makes two entries in content.xml, and those entries must go in very specific places in the file in order for Navigraph to work correctly. This is necessary for Navigraph AIRAC data to take priority over the default NavBlue data.

One entry is near the top of content.xml, and one is near the bottom. If you delete content.xml and let MSFS rebuild it on the next run, it might detect the files and folders that Navigraph has installed, but it will not put the links to those Navigraph files in the correct places in content.xml. The result could be that Navigraph data will not be used by the sim (even though it appears to be installed), or you could end up with a mix of Navigraph and NavBlue data that could cause unexpected behavior of navaids or approaches.

The way to avoid this is to uninstall Navigraph first with their MSFS data manager. Run MSFS once to rebuild content.xml. Exit MSFS and reinstall Navigraph with their data manager, which will place the entries to Navigraph in content.xml in the correct locations.

Edited April 16, 20224 yr by JRBarrett

8 minutes ago, JRBarrett said:

it might detect the files and folders that Navigraph has installed, but it will not put the links to those Navigraph files in the correct places in content.xml.

Ran a test earlier and it looked like only the entry near the end of the file was detected - and of course it also leaves both the fs-base-nav and navigraph entries as active, so, yes it looks like a recipe for trouble ...

Man, I’ve a headache reading half of that complicated mess. It all seems totally unnecessary to me 💁‍♂️

Yeah. Could anyone clarify - why run the powershell "cleaner" script in the first place?

1 hour ago, Ianrivaldosmith said:

Man, I’ve a headache reading half of that complicated mess. It all seems totally unnecessary to me 💁‍♂️

Not that I would ever figure out how to do any of this powershell stuff, but what are we trying to achieve here? I have been flying in MSFS since the alpha, and don't recall ever having had to clear caches, cml files, etc., nor have I emptied the Community folder when doing a sim update. I do use the add-ons linker and am careful only to link those add-ons being used on that flight.

Things seem to work fine. What am I missing here?

22 minutes ago, jrw4 said:

Things seem to work fine. What am I missing here?

Nothing. Nothing meaningful that I can see 

23 hours ago, turbomax said:

you can easily do that yourself and delete those files, the files are here (MSFS store version):

C:\Users\<your user name>AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache

I deleted those files and noticed no difference when restarting the sim. 

Seems like a voodoo fix to me. 

Unless you really know what you're doing, or don't care about having to reinstall the sim, my advice would be to stay away from this kind of messing around. 

Edited April 16, 20224 yr by Ricardo41

4 hours ago, JRBarrett said:

Navigraph’s data manager makes two entries in content.xml, and those entries must go in very specific places in the file in order for Navigraph to work correctly. This is necessary for Navigraph AIRAC data to take priority over the default NavBlue data.

One entry is near the top of content.xml, and one is near the bottom. If you delete content.xml and let MSFS rebuild it on the next run, it might detect the files and folders that Navigraph has installed, but it will not put the links to those Navigraph files in the correct places in content.xml. The result could be that Navigraph data will not be used by the sim (even though it appears to be installed), or you could end up with a mix of Navigraph and NavBlue data that could cause unexpected behavior of navaids or approaches.

The way to avoid this is to uninstall Navigraph first with their MSFS data manager. Run MSFS once to rebuild content.xml. Exit MSFS and reinstall Navigraph with their data manager, which will place the entries to Navigraph in content.xml in the correct locations.

I am aware of that. I just ran my cleaner and then used addon linker to start MSFS with only 1 airport installed. There are 2 Navigraph entries just as you say. One near the top, and one at the bottom. I don't recall ever not seeing fs-base-nav. I think its always been there on my system, but the Navigraph entry below it should take precedent when the sim runs since it is after fs-base-nav in the file.

I pasted my content.xml in the spoiler.       

Spoiler

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Content>
  <Package name="fs-base" active="true"/>
  <Package name="fs-base-ai-traffic" active="true"/>
  <Package name="fs-base-genericairports" active="true"/>
  <Package name="fs-base-nav" active="false"/>
  <Package name="navigraph-navdata-base" active="true"/>
  <Package name="fs-base-ui-vr" active="true"/>
  <Package name="asobo-jetways" active="true"/>
  <Package name="asobo-liveevent" active="true"/>
  <Package name="asobo-modellib-airport-generic" active="true"/>
  <Package name="asobo-modellib-buildings" active="true"/>
  <Package name="asobo-modellib-props" active="true"/>
  <Package name="aerosoft-paderborn" active="true"/>
  <Package name="asobo-airport-biis-isafjordur" active="true"/>
  <Package name="asobo-airport-c53-lowerloon" active="true"/>
  <Package name="asobo-airport-cytz-billy-bishop" active="true"/>
  <Package name="asobo-airport-czst-stewart-aerodrome" active="true"/>
  <Package name="asobo-airport-eg78-outskerries" active="true"/>
  <Package name="asobo-airport-eidl-donegal" active="true"/>
  <Package name="asobo-airport-fxme-maketane" active="true"/>
  <Package name="asobo-airport-huen-entebbe" active="true"/>
  <Package name="asobo-airport-kase-aspen" active="true"/>
  <Package name="asobo-airport-kcof-patrickafb" active="true"/>
  <Package name="asobo-airport-kdfw-dallas-fort-worth" active="true"/>
  <Package name="asobo-airport-keb-nanwalek" active="true"/>
  <Package name="asobo-airport-kjfk-new-york-jfk" active="true"/>
  <Package name="asobo-airport-klax-losangeles" active="true"/>
  <Package name="asobo-airport-kmco-orlando" active="true"/>
  <Package name="asobo-airport-knfl-nas-fallon" active="true"/>
  <Package name="asobo-airport-knkx-miramar-mcas" active="true"/>
  <Package name="asobo-airport-ksea-seattle-tacoma" active="true"/>
  <Package name="asobo-airport-ksez-sedona" active="true"/>
  <Package name="asobo-airport-kswf-stewartintl" active="true"/>
  <Package name="asobo-airport-ktex-telluride" active="true"/>
  <Package name="asobo-airport-kxmr-cap-canaveral" active="true"/>
  <Package name="asobo-airport-lfcs-saucats" active="true"/>
  <Package name="asobo-airport-lflj-courchevel" active="true"/>
  <Package name="asobo-airport-lfpg-paris-charles-de-gaulle" active="true"/>
  <Package name="asobo-airport-lowi-innsbruck" active="true"/>
  <Package name="asobo-airport-lpma-madeira" active="true"/>
  <Package name="asobo-airport-lxgb-gibraltar" active="true"/>
  <Package name="asobo-airport-mhtg-toncontin" active="true"/>
  <Package name="asobo-airport-mrsn-sirena-station" active="true"/>
  <Package name="asobo-airport-nzqn-queenstown" active="true"/>
  <Package name="asobo-airport-rjtt-tokyo-haneda" active="true"/>
  <Package name="asobo-airport-rjx8-suwanosejima" active="true"/>
  <Package name="asobo-airport-rokr-kerama" active="true"/>
  <Package name="asobo-airport-rors-shimojishima" active="true"/>
  <Package name="asobo-airport-sbgl-riodejaneiro" active="true"/>
  <Package name="asobo-airport-seqm-mariscal-sucre-quito" active="true"/>
  <Package name="asobo-airport-spgl-chagual" active="true"/>
  <Package name="asobo-airport-tffj-gustaf" active="true"/>
  <Package name="asobo-airport-tncs-saba" active="true"/>
  <Package name="asobo-airport-vnlk-lukla" active="true"/>
  <Package name="asobo-airport-vqpr-paro" active="true"/>
  <Package name="asobo-airport-wx53-bugalaga" active="true"/>
  <Package name="asobo-airport-yssy-sydney" active="true"/>
  <Package name="asobo-vfx-staticmesh" active="true"/>
  <Package name="fs-base-coverage-map-australia-tin" active="true"/>
  <Package name="fs-base-coverage-map-france-tin" active="true"/>
  <Package name="fs-base-coverage-map-germany-tin" active="true"/>
  <Package name="fs-base-coverage-map-japan-tin" active="true"/>
  <Package name="fs-base-coverage-map-uk-tin" active="true"/>
  <Package name="microsoft-airport-eddp-leipzig" active="true"/>
  <Package name="microsoft-airport-edds-stuttgart" active="true"/>
  <Package name="microsoft-airport-edhl-luebeck-blankensee" active="true"/>
  <Package name="microsoft-airport-edja-allgau" active="true"/>
  <Package name="microsoft-airport-edvk-kassel" active="true"/>
  <Package name="microsoft-airport-edxh-helgoland" active="true"/>
  <Package name="microsoft-airport-efva-vaasa" active="true"/>
  <Package name="microsoft-airport-egcb-barton" active="true"/>
  <Package name="microsoft-airport-eggp-john-lennon" active="true"/>
  <Package name="microsoft-airport-eghc-lands-end" active="true"/>
  <Package name="microsoft-airport-egpr-barra" active="true"/>
  <Package name="microsoft-airport-ehrd-rotterdam" active="true"/>
  <Package name="microsoft-airport-ekrn-bornholm" active="true"/>
  <Package name="microsoft-airport-ensb-svalbard" active="true"/>
  <Package name="microsoft-airport-essa-arlanda" active="true"/>
  <Package name="microsoft-airport-katl-atlanta" active="true"/>
  <Package name="microsoft-airport-kfhr-friday-harbor" active="true"/>
  <Package name="microsoft-airport-lfhm-megeve" active="true"/>
  <Package name="microsoft-airport-lfmn-nice" active="true"/>
  <Package name="microsoft-airport-lowk-flughafen-klagenfurt" active="true"/>
  <Package name="microsoft-airport-lsza-lugano" active="true"/>
  <Package name="microsoft-airport-lszh-zurich" active="true"/>
  <Package name="microsoft-airport-lszo-beromuenster" active="true"/>
  <Package name="microsoft-airport-lszr-altenrheinst-gallen" active="true"/>
  <Package name="microsoft-airport-n15-kingston" active="true"/>
  <Package name="microsoft-airport-rjck-kushiro" active="true"/>
  <Package name="microsoft-airport-rjfu-nagasaki" active="true"/>
  <Package name="microsoft-airport-rjth-hachijojima" active="true"/>
  <Package name="microsoft-airport-voloport" active="true"/>
  <Package name="microsoft-airport-ylre-longreach" active="true"/>
  <Package name="microsoft-airport-ymbt-mountbeauty" active="true"/>
  <Package name="microsoft-airport-ypbo-paraburdoo" active="true"/>
  <Package name="microsoft-airport-yshl-shellharbour" active="true"/>
  <Package name="microsoft-australia-point-of-interest" active="true"/>
  <Package name="microsoft-countryside-point-of-interest" active="true"/>
  <Package name="microsoft-discovery-barcelona" active="true"/>
  <Package name="microsoft-franckfurt-point-of-interest" active="true"/>
  <Package name="microsoft-germany-point-of-interest" active="true"/>
  <Package name="microsoft-discovery-berlin" active="true"/>
  <Package name="microsoft-discovery-coimbra" active="true"/>
  <Package name="microsoft-discovery-darwin" active="true"/>
  <Package name="microsoft-discovery-freiburg" active="true"/>
  <Package name="microsoft-discovery-gibraltar" active="true"/>
  <Package name="microsoft-discovery-goldcoast" active="true"/>
  <Package name="microsoft-nordic-point-of-interest" active="true"/>
  <Package name="microsoft-discovery-helsinki" active="true"/>
  <Package name="microsoft-discovery-lisbon" active="true"/>
  <Package name="microsoft-discovery-madrid" active="true"/>
  <Package name="microsoft-discovery-mecca" active="true"/>
  <Package name="microsoft-discovery-melbourne" active="true"/>
  <Package name="microsoft-usa-point-of-interest" active="true"/>
  <Package name="microsoft-discovery-monument" active="true"/>
  <Package name="microsoft-discovery-mountcook" active="true"/>
  <Package name="microsoft-discovery-pennine" active="true"/>
  <Package name="microsoft-discovery-perth" active="true"/>
  <Package name="microsoft-discovery-singapore" active="true"/>
  <Package name="microsoft-discovery-sydney" active="true"/>
  <Package name="microsoft-discovery-uluru" active="true"/>
  <Package name="microsoft-france-benelux-point-of-interest" active="true"/>
  <Package name="microsoft-griffith-observatory" active="true"/>
  <Package name="microsoft-japan-point-of-interest" active="true"/>
  <Package name="microsoft-uk-point-of-interest" active="true"/>
  <Package name="mjascenery-airport-kbwi-baltimore" active="true"/>
  <Package name="navigraph-navdata" active="true"/>
</Content>

 

29 minutes ago, Ricardo41 said:

I deleted those files and noticed no difference when restarting the sim. 

Seems like a voodoo fix to me. 

If you weren't having any problems, you absolutely won't see anything happen.

I'm not sure why MSFS might be acting differently for others than it has for me, so if MSFS isn't putting everything back where it should be, including Navigraph, on your system then I wouldn't do it any more.     

Edited April 16, 20224 yr by MDFlier

5 hours ago, JRBarrett said:

Navigraph’s data manager makes two entries in content.xml, and those entries must go in very specific places in the file in order for Navigraph to work correctly. This is necessary for Navigraph AIRAC data to take priority over the default NavBlue data.

One entry is near the top of content.xml, and one is near the bottom. If you delete content.xml and let MSFS rebuild it on the next run, it might detect the files and folders that Navigraph has installed, but it will not put the links to those Navigraph files in the correct places in content.xml. The result could be that Navigraph data will not be used by the sim (even though it appears to be installed), or you could end up with a mix of Navigraph and NavBlue data that could cause unexpected behavior of navaids or approaches.

The way to avoid this is to uninstall Navigraph first with their MSFS data manager. Run MSFS once to rebuild content.xml. Exit MSFS and reinstall Navigraph with their data manager, which will place the entries to Navigraph in content.xml in the correct locations.

OK thanks. I have to say that deleting the content.xml and scenery indexes seems to have solved my loading CTDs issue touch wood.

10 hours ago, MDFlier said:

Yes, the indexes get rebuilt on startup. 

I use add-on linker. Every time i start the sim, there is different scenery in the community folder than what was in there the last time I flew. The old indexes based on the old config are wrong for scenery that the sim will be using so I clean them before flying.

My routine is to update FBW, then run the cleaner, then run addon linker, and launch the sim from it.

Addon Linker has options to delete content.xml as well as SceneryIndexes. I'm on travel right now and don't have my Flightsim machine available but as far as I recall these are two options to be edited in the .ini(?) script. This one can be opened via the GUI.

I have both of them active to be deleted, Of course, this works only if you start MSFS via the linker GUI (the very right menu icon).

Best regards, Michael

7 hours ago, JRBarrett said:

The way to avoid this is to uninstall Navigraph first with their MSFS data manager. Run MSFS once to rebuild content.xml. Exit MSFS and reinstall Navigraph with their data manager, which will place the entries to Navigraph in content.xml in the correct locations.

this should be included in that powershell script, that is the most tedious part to have to do it manually every time you change anything in the Community folder. that would be a real time saver.

Edited April 16, 20224 yr by turbomax

2 hours ago, MDFlier said:

am aware of that. I just ran my cleaner and then used addon linker to start MSFS with only 1 airport installed. There are 2 Navigraph entries just as you say. One near the top, and one at the bottom.

Yes, Navigraph places its entries in the correct place in content.xml, and also marks the default fs-base-nav folders as “inactive”.

With recent versions, the Navigraph data manager for MSFS also runs as a background process all the time, (visible in the lower right corner of the taskbar), and I believe one of the reasons for this is to automatically adjust the specific Navigraph entries in content.xml if that file is edited or deleted - if that is the case, it may no longer be necessary to uninstall / reinstall Navigraph when deleting the content.xml file. 

1 hour ago, JRBarrett said:

Yes, Navigraph places its entries in the correct place in content.xml, and also marks the default fs-base-nav folders as “inactive”.

Yep. Missed that. I was thinking that it got deleted based on your comments. I never looked at that before.

If you are really want to do it the easy way, uninstall Navigraph, move or unlink all of your addons, delete content.xml and restart MSFS to let it build a fresh base copy of content.xml. Then, exit MSFS, install Navigraph and make a backup copy of the new clean content.xml with the Navigraph entries. Now, add a 3rd line to the script that restores the backup copy at the end. This way, you start off fresh and have Naviograph ready to go. 

Line 3 could be:

  Copy-Item "E:\MSFS\BaseContent.xml" "C:\Users\<username>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Content.xml"

Edited April 16, 20224 yr by MDFlier

14 hours ago, MDFlier said:

Yep. Missed that. I was thinking that it got deleted based on your comments. I never looked at that before.

If you are really want to do it the easy way, uninstall Navigraph, move or unlink all of your addons, delete content.xml and restart MSFS to let it build a fresh base copy of content.xml. Then, exit MSFS, install Navigraph and make a backup copy of the new clean content.xml with the Navigraph entries. Now, add a 3rd line to the script that restores the backup copy at the end. This way, you start off fresh and have Naviograph ready to go. 

Line 3 could be:

  Copy-Item "E:\MSFS\BaseContent.xml" "C:\Users\<username>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Content.xml"

And, anytime MSFS is updated (either SU or WU) do the same again as the update may have added new default entries to Content.xml.

...jim