GSX has been compatible with the SU10 Navdata API since last October, just a couple of weeks after SU10 came out, so it was likely the first 3rd party app ever able to work with Marketplace airports.
The option to use the SU10 Navdata API is not enabled by default, because there are currently side effects using it, basically related to jetway detection, since with the SU10 Navdata, we don’t have anything other than a flag saying if a certain parking spot has a jetway or not, nothing else.
This means we need to do a very unreliable heuristic search for jetways based on their likely names, so we could detect their status, using another unreliable heuristic based on their animated hood.
This doesn’t work very well, since it’s basically impossible to detect things like the “real” jetway on a parking spot with two jetways with one static, doesn’t work with jetways that for some reason failed to animate the hood, and doesn’t work with some jetways placed in less than standard positions in relationship to their parking spot.
But most of all, we don’t have ANY way to know WHERE a jetway docked, or if it has docked partially, we can only assume ( better say “hope” ) you parked in a position where the jetway went correctly to the Main passenger door, provided all the previous assumptions about which SimObject is actually a jetway and we could detect its docking status by checking the hood variables, which is not granted.
In every situation where any of this fails ( wrong jetway detected or not detected at all ), or the jetway docked to the wrong door or docked partially, you will either see ZERO passengers, or you’ll see passengers walking in the air, because without any data about the jetway actual location, we can only create waypoints for passengers under the assumption the jetway docked on the Main exit, which is not always the case.
This will change completely with SU12 !!
With SU12, we’ll get actual positions for all Jetways and which parking they are associated to, so no more heuristic (and slow) search.
We’ll get the actual jetway status ( undocked, in movement, docked, etc. ), so no more unreliable detection based on their animated hood, which might not always animate.
But most importantly, we’ll get the actual position of the two “Bones” that control the jetway Inverse Kinematics, which means we’ll know where the Jetway “Head” is after it moved, and we’ll know which door it has docked to.
With all these data, we’ll be able to place passengers waypoints correctly, without guessing, even when the jetway docks in strange positions, like the AFT door. If it happens, the passengers will walk from there so, no more passengers walking in the air.
And BTW, we already have a working version, running in SU12 Beta right now, we might even release a Public test, so those running the SU12 Beta could try it.