What is SU12 Navadata API option good for except for locating jetways at Standard Microsoft/Asobo and 3rd party Marketplace bought airports? If there is no other use for it, how can I disabled it?
And why you would want to go back to the legacy "airport cache" method, which would:
- slow down the startup
- have to be regenerated each time you install/remove a scenery
- affected by any possible issues in your Community folder, like file access problems, possibly corrupted files or just not finding the right .BGL ?
- not future-proof, because it relied opening a non-officially documented file format, which can possibly change at any time ( it has already changed several times since MSFS came out ) ?
While in the SU10 version of the Navdata, it might have been useful to disable it if you didn't use Marketplace airports, because by reading the .BGL we had jetways working a bit better, because at least we could read their positions from the .BGL, which we couldn't in SU10, with SU12 we can, and we also get even more data than we ever had ( even from the .BGL ), because the issues with jetways were not just caused by not finding them ( that was just one of the issues ) but also not being able to detect their status reliably and not knowing where the jetway went after it animated, which caused passengers in the air each the jetway didn't go to the Main Exit.
Since SU12 fixes all of that, it doesn't really makes sense to disable it.
The only side effect of using the Navdata, is that if you use a GSX custom profile, you must to be sure it's for the correct scenery you have installed at the time, since we can no longer associate a .BGL with an .INI, only the ICAO code matters, so you need to be sure the profile you use was made for that scenery.
