It's easily fixed by excluding GSX jetway replacement for such airports, but I just wanted to know if this is a known side effect, or perhaps something that can be solved by the scenery builder?
If you noticed this is fixed that way, meaning the duplicate parking spots were caused by the GSX Jetway replacement files themselves, the possible reasons why this happens are:
- The 3rd party airport package doesn't conform to the official package naming convention of
developer-airport-ICAO-airportname, this is common for freeware, since Marketplace add-ons not conforming to this standard won't be accepted on the MS Marketplace. A package named in a non-standard way cannot be detected by GSX "Exclude 3rd party button", so it must be Disabled by-ICAO manually in the GSX Config panel.
- You might have installed or relinked the 3rd party airport after you last ran the GSX Update. The "Exclude 3rd party button" is a button you call manually, but it is also a procedure that runs automatically when you first install GSX Pro, when you Relink or Unlink GSX Pro with the FSDT Installer, or when you perform an Update for GSX Pro. But if you added a new 3rd party airport in the meantime, it won't be excluded from GSX Jetway replacement, until the next time you run the FSDT Updater, or enter the installer and click again the "Exclude 3rd party button". This, of course, assuming the airport CAN be automatically detected as explained in the previous point. If it's not, it must be Disabled manually by ICAO.
