The passenger walking path already supports a jetway bridge but, of course, it must be a GSX bridge, which has its dimensions and placement entirely known to GSX.
If you place only a Jetway with GSX, and use the bridge that comes with the scenery, this is usually part of a terminal mesh, so there's no way for GSX to know how and where it's placed. In fact, GSX doesn't even know the bridge exists.
I think this might be *possibly* solved in two ways:
- With a full blown passenger path editor, not very different from the new multi-waypoint editor for the custom pushback, with additional controls to set the height from ground at each waypoint and its width. GSX already supports all of that, internally, which is how the walking passenger inside the Terminal C at KORD V2 work, and this should be our long term goal, since it will also allow for custom walking path for passenger reaching the terminal on foot after using a staircase, when a Bus is not required.
- Setting an "invisible" property to the GSX jetway bridge, so you could use it as a dummy to match bridges coming from 3rd party sceneries, using the GSX bridge information without creating the actual object, just to allow the passengers to complete the path. However, something like this would become useless once we'll have the above "real" editor.
