• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS20 Modification of KTNT to add ILS and NDB was Successful but discovered a constraint with Navigraph

M

machtoo

Messages
14
Country
us-northcarolina
I have successfully modified KTNT to add an ILS and NDB for the IAF. However, none of the Navaids worked until yesterday. After much reading and thought I tried an experiment. I use Navigraph data for MSFS 2020 and other addons. The Navigraph data files exist in the Community folder. As a test, I removed the Navigraph folder from the Community folder and looked in Little Navmap at KTNT after telling it to not use Navigraph data only MSFS data.

Voila...my ILS and NDB were visible. So, I loaded a flight in MSFS 2020 at KTNT with the Cessna 172 and tuned the ILS and NDB in the ADF...they worked. Only issue was the glide slope did not kick in on the approach. Still have to figure that one out. May be placement. I put it at the start of the runway.

The revelation from two weeks of thinking my package was not working was MSFS 2020 will not use its own nav data if the Navigraph folder are present. Either MSFS or Navigraph needs the ability to tell MSFS 2020 to use its own navdata for custom packages in the Community folder and ignore Navigraph.

Now to work on the glideslope issue and we will have a fully operational KTNT.
 
I would knock on navigraph's door on that to either to get custom setups or incorporate the changes, if applicable. 😉
 
Navigraph overrides all navigation when used. It's been that way for years.
 
You must log in or register to reply here.
Back
Top