It seems all users reporting problems are all using UK2000. Are you sure these sceneries are even customizable in the first place ? A scenery that already has SODE jetways, for example, cannot be customized at all.
With respect, looking at the plethora of problems currently being reporting, suggesting that they're all related to UK2000 airports is totally incorrect.
In regard to SODE, UK2000 airports, although using SODE objects, currently do not support SODE jetways (ctrl-j to operate).
With respect to the latest update, it's made absolutely no difference. Here's a picture of the customised jetway before exiting the sim. However, shut the sim down, come back and once again, there's no jetway.
Looking at the exclude xml file created, there's definitely something not right going on. I only excluded gate 20, but the file also has an exclude entry for gate 32. I have repeated the process several times, and on each occasion, the same two gates are excluded and then compiled. And I can assure you that I did
not have gate 32 selected before the exclude creation:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- Created by GSX on 2018-09-12 -->
<FSData version="9.0" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="bglcomp.xsd">
<!-- Exclude Jetway Gate 20 -->
<ExclusionRectangle latitudeMinimum="51.1548160189" latitudeMaximum="51.1548339962" longitudeMinimum="-0.169097629062" longitudeMaximum="-0.169069042849" excludeAllObjects="TRUE"/>
<!-- Exclude Jetway Gate 32 -->
<ExclusionRectangle latitudeMinimum="51.1576317889" latitudeMaximum="51.1576497662" longitudeMinimum="-0.168673832007" longitudeMaximum="-0.168645244054" excludeAllObjects="TRUE"/>
</FSData>
I have also attempted to manually remove the gate 32 entry, then recompile without it. The compiled file then correctly displays one excluded jetway. But it makes no difference to the final outcome...
