As explained so many times in the forum, GSX doesn't change ANYTHING in the way jetway operates, it only changes the way Jetways LOOKS, provided you are on a default airport with default Jetways that have been replaced by GSX.
I tried on differents cases :
- Default airport (with ICAO.bgl in the ENABLED column of the FSDT Installer)
- 3rd party airport (with jetways replacements ENABLED)
- 3rd party airport (with jetways replacements DISABLED)
Case #3 should have proved to you the problem doesn't have anything to do with GSX. And case #2 should never be used, since you are always supposed to Disable GSX Jetway replacements for 3rd party airports.
GSX doesn't animate the jetway. It JUST sends a "JETWAY TOOGLE" command to the sim, exactly as if you were using the default ATC menu to operate the jetway. Whether the Jetway moves or not, or connects to, or connects partially or completely, is completely outside GSX control, and won't change a bit, regardless if you used the GSX menu or not, since in all cases, the jetway is always controlled by the simulator itself.
The only thing that matters, is the parked positions and the airplane door configuration.
Which means, one thing you CAN do from GSX to improve things, is CUSTOMIZE the Parking STOP position, and find one that will result in the Jetway working. That's why the Parking Customization Editor has a TEST function ( NumPad5 while editing the Parking itself ), which you can use to tune your custom STOP position to fine one that works.