I now have a problem in that when I now import other third-party airport (w/SODE option(s) as well) sceneries, I have a 50/50 chance that the scenery will install correctly (as far as the air bridges) are concerned.
Please be more clear. By saying "w/SODE option(s) as well", you mean some sceneries that have SODE jetwasy opposed to other sceneries that don't have SODE (and you have problems with both), or the same scenery that is giving you an option to use either SODE jetways or CTRL+J jetways ?
In any case, depending on the option, none of your problems are caused by GSX, because:
- If the airport use SODE jetways, GSX won't do anything to it, and won't even allow you to do anything to it, unless you explicitly remove its SODE XML configuration file. So, whatever issues you have on a scenery that use SODE jetways, it's nothing to do with GSX and would allow just as GSX was never installed, since those jetways are *created* by the scenery with SODE, configured in the SODE XML file that comes with the scenery, and are entirely activated by SODE. The only information we get about them, is their number, location and their height so we can walk passengers through them, but we don't have any control over their appearance or how they work.
- If the airport use CTRL+J jetways, GSX again won't do anything to them by default. You must go through the whole exclusion procedure, which will then allow you to put a GSX/SODE jetway in place of the old one. But before you do that, nothing in GSX has changed anything on a 3rd party scenery jetway that uses CTRL+J modes. The only models we replace automatically are those on default airports.