That would cause a mess on VATSIM.
Even with a choice button?
Not everyone uses Navigraph.
Then it wouldnât affect them one way or the other. It would hopefully be an optional benefit to those who want it.
Not mandatory ⊠choice!
The thing with navdata from Navigraph is that there is only one free AIRAC cycle which is like a year old otherwise you only have access to the AIRAC cycles that you have paid for. They would have to get with Jeppesen and see if itâs ok to release all the old navdata for free including navdata that is just one cycle out of date (which I doubt they would do).
Yes, I see your point but if itâs a standard navigraph data free airac cycle, that wouldnât change. If they had a legacy mode, it would still be unlikely to affect it much since new vorâs, ndbâs etc are unlikely to be added ( unless some were missed) and, since it is a legacy thing, hopefully they would make it free to all.
This would just sit in the background until you want to use it.
Edit. I am sure they already have tons of old licenced data they could haul out of the archives.
This discussion seems a bit off topic for this thread about ILS alignment. In any case, you canât just combine old data and new data together, as you will get frequency and ident clashes.
Im not suggesting combining them.
Im suggesting 2 different modes. Modern and legacy.
Ah, okay. Producing an old navdata package is already possible for a third party that has such data.
For the ones participating to the beta:
Continuing the discussion from Release Notes - SU6 Beta 1.8.5.0 - July 6, 2026:
Just want to add some context to the above:
The changelog entryâs necessary brevity makes it sound like it was just forgotten to align some ILS. As explained prior in this thread, thatâs not really the case.
We took a systematic approach to trying to address this issue on multiple fronts:
- Fixing some mathematical issues in the vertical part of the ILS guidance in the simulator radio system that could cause strange deviations even when stable near the runway
- Taking a look at the source data to try to come up with some reasonable inference heuristic to determine what is actually offset and what isnât, to an acceptable level of error (since the data doesnât tell us directly)
- Take those that the heuristic tells us should not be offset, load the sim scenery XMLs, and snap the ILS to the scenery runway
- Spot-check the heuristic to make sure we donât have a bunch of snapped things that shouldnât be snapped, and vice versa
Given that this is done heuristically, it is of course possible that there are a non-zero number of erroneous snappings, but our spot checking did not reveal any. If you see some, please let us know in the beta forums.
This was a sizable project and we hope that folks find the results in SU6 to be a substantial improvement.
Is it possible this could have been contributing to some of the reports of the B738M falling below G/S on short final?
Not that I can think of. What it mostly fixes is reports of the vertical deviation suddenly âfalling off the tableâ as it were or shooting up near the final 100-200 feet or so. As far as I remember the B738 reports donât reference this phenomenon.