I bought FT KBOS a couple of days ago right after the latest MSFS update. I seem to have problems with the sids at the airport. I was using revss.revss sid. It can be used for 15R, 4R, 33L, 22L, 9, 17. However, after loading the sid, there were missing waypoints, especially revss, which is the final waypoint. I use Navigraph, and I was using the TBM 930. I tried the g1000NXi, and it showed the waypoints, but the locations weren’t showing so they didn’t show in the flight plan.
This is a shot in the dark here, but I have seen issues with airports depending on where the package name is in the content.xml file relative to where the Navigraph package is. If the airport is the last line in the content.xml file, then it might overwrite the Navigraph info with its own.
Make sure your airports are not last, or are at least before the final Navigraph package name.
I can attest to what BigCow74 here is saying. If you’ve downloaded any addon airport for which there is a MSFS custom “bespoke” airport, make sure you’ve moved your purchased add-on airport to a higher position than the bespoke airport in your content.xml file. If you need help doing this, search the forums and you’ll find it. This is usually the problem with SIDs/STARs and add-on airports.
Top of content.xml and very bottom of content.xml
Everything else in between.
<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="navigraph-navdata" active="true"/>**
</Content>
You end up mostly having to remove the star airports if in fact you want to avoid all conflicts. That is, if you’re using a payware airport that replaces the star airport. Furthermore, if you’ve already flown out of the star airport and then replace it with a payware addon, if you have scenery cache enabled it’s good practice to clear this cache before preceding to fly out of the payware airport you replaced the star airport/bespoke airport with.
Cheers!
1 Like
I have Navigraph and the WT G3000 installed and each of these SIDs loaded perfectly for me. You made a mention of the WT G1000? The TBM uses the G3000. I’m not clear what you’re using. I.e, the default G3000 or the latest WT G3000.
I uninstalled kbos, then loaded to see if that fixed the missing waypoints. Mainly REVSS, they were still missing, so FT kbos isn’t the problem. I guess there has to be some file causing the problem. I’m just going to keep flying.
Not sure if you checked your content.xml file or not, but if you are not comfortable doing that, you might want to try and use the Navigraph nav data installer to “remove” your current Navigraph install and then re-install it. That should (?) get your content.xml file right again, as I think it appends the Navigraph package info to the end of the file as part of the install process.
THIS… 
That worked.