There's no reason for GSX to control jetways, since FSX already supports animated jetways, all default airports have them, and any developer can add them to its scenery.
Doing animated jetways was very complex in FS9 so, it's understandable that developers working doing FS9 sceneries would not use them, but with FSX there's really no reason to advertise a scenery being for FSX and not having what even a default FSX scenery has. It would also be wrong asking users to spend additional money to get a feature that should come with the scenery.
In fact, more and more developers are adding animated jetways as standard, which is obviously a result of the huge success GSX had ( is still selling today like the 1st day ), we always had animated jetways in all our sceneries since 2007. UK2000 and Flightbeam, which are two of the most talented scenery developers out there, have them too, and FlyTampa finally add them in their latest TCNM so, it's clear the trend is towards having animated jetways as standard, at least for the top scenery developers.
Also, if we had to support each 3rd party airport moving jetways, we would have to charge by airport JUST for moving jetways (because the rest of GSX would of course still work anyway), which is wrong.
If we had to charge users, it would be much better to charge for a brand new GSX version with totally new features, or an expansion product like cargo operations, GA operations, military operations, etc, which, thanks to the global nature of GSX, will still be a one-time purchase and will immediately support all 20.000 FSX airports from day one.
