Hello,
does Navigraph work with default aiports or is it likely that runway positions or ILS localizers are offset in the sim?
I used to have a 3rd party airport, where everything was aligned. Then I unistalled it and the ILS was offset.
I’m not sure if I should’ve deleted and reinstalled the AIRAC in the Navigraph Hub to rebuild the database for the now default aiport or if it is a general issue with default scenery in MSFS that can happen.
Happy new year and thank you in advance.
Hello Cubey.
When you run Navigraph Hub this piece of software will replace the internal navigation database in MSFS2020 such that there is no longer any default airports. This means that your question "does Navigraph work with default aiports " is a bit ill-posed, unless I am misunderstanding you of course.
When it comes to 3rd party airports, the scenery developer should ideally not specify any coordinates, but rather rely on the underlying navigation data, be it Navigraph or MSFS2020 default navigation data.
I suggest that you uninstall the navigation data using the function in Navigraph Hub, reinstall it, and then install your 3rd party airport, and tell us what you see. Maybe you could share the name of the third party developer too. It may be a known issue.
Kind regards
Magnus
Hello thanks for the answer.
I was experiencing this probem after unistalling a 3rd party scenery where everything worked fine and reverting back to the default aiport. There on the default airport the ILS was misaligned.
So my question was. Does this happen because the default airport’s state (and therefore database) is too old for the current AIRACs and that these issues happen with default airports (because of runway heading changes over time, etc.)
Or if it was because the navigraph database was still applying the 3rd party data to the default airport because I didn’t rebuild the database after switching from 3rd party to default.
Hope that clarifies it.
Does this happen because the default airport’s state (and therefore database) is too old for the current AIRACs and that these issues happen with default airports (because of runway heading changes over time, etc.)
No, I don’t think so, because the internal MSFS2020 navigation database is updated regularly and runway headings don’t change too often.
Or if it was because the navigraph database was still applying the 3rd party data to the default airport because I didn’t rebuild the database after switching from 3rd party to default.
To my understanding both navigation data and airport scenery are stored as BGL files. They are read on simulator startup, and then continuously according to a QMID algorithm. Unless you have swapped the BGL files while the simulator was running, you should not be able to achieve a mixed state of default and 3rd party data.
But I do seem to remember that on an object level there is a logical division between the airport object and its approach, and the ILS. If I could get the specific airport and scenery names, then we could look into runway heading, localizer positions, and the procedure.
/M.
It was a HEGN. The 3rd party scenery from simbreeze worked fine. Everything was ok. After uninstalling the 3rd party and flying to the default airport HEGN, the ILS34R (or ILS 34, since the default HEGN doesn’t have the second rwy yet, I believe) the localizer was not aligned and was approaching the rwy at an angle. The plane I used was the Fenix A320.
Hi,
When the stock scenery is outdated, as in your example, the chance that the localizers are not aligned is high; that’s about “normal,” and there is no data issue; in this case, you should report this to ASOBO/MS.
We have all the correct runways in our data, and you see this in the Fenix, but when the underlying scenery is outdated and not reflecting the real world, we can’t do anything (we may not change the runway idents, nor may we add new runways).
This is for both sims, which are the same, 2020 and 2024.
In other words, as long as the scenery reflects the real world, it should be okay when the airport layout is outdated, so you should inform ASOBO/MS.
Cheers
Richard
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.