GSX web page CLEARLY explain this:
https://fsdreamteam.com/products_gsxpro.htmlWhile GSX works automatically with every airport, it needs to read the airport .BGL file, which means, by default, airports bought on the MS Marketplace won't work well, because GSX would use data from the default airport, since it can't read the add-on scenery because of the Marketplace DRM encryption. This is not an issue for FSDT airports, because we'll install a DRM-free version of the airport file automatically for all our sceneries but, for 3rd party sceneries, you might need to ask the original developers if they would be willing to make available a file with at least the basic airport data, which can be used by GSX when placed in the GSX profiles folder.
While there shouldn't even be a need to say that, because it's common knowledge NO add-on can read encrypted .BGLs ( does Little Nav Map shows the correct parking of that scenery ? Is that a "joke" for you as well ? ) and we started warning users about this since MSFS came out 2 years ago, this issues has been discussed so many times and, so many times we already explained:
- You have a workaround now, that is obtaining an unencrypted version of just the airport file from the original scenery developer. We obviously install such files for all our airports automatically, and some developers like LatinVFR or FlyTampa are supplying their user with such files.
- AFTER SU10 will come out, there will be a new API in he SDK which will allow add-ons to obtain data about an airport without having to read the airport file directly, which will make airports bought in the Marketplace compatible with ANY utility that need to read the airport data for any reason, including GSX, but not only.
We are already working with the Beta version, and once SU10 will came out officially, we can finish the integration in GSX and release an update to use it.
