I am a gsx pro user in msfs 2020. The jetway is not operating at the arrival airport. I get a 'Bad jetway data' warning. What's the problem? It started happening after the last update.
You are confusing the message with the problem.
The problem doesn't have anything to do with GSX, which simply got this error from Simconnect when it asked a list of jetways on the airport, and this would have happened before as well, the ONLY difference is that, in previous versions, you had to enable GSX logs and check the log to see the warning, so the only thing you saw were jetways that didn't work, assuming it was a GSX bug.
In order to prevent users to be mislead assuming it's a GSX bug, and provide some feedback about the problem that would possibly lead to investigate it ( a scenery conflict could cause this, but also even a *single* missing jetway in the scenery will also cause it), and of course check (in MSFS 2020) that GSX replacement jetways has been excluded for that airport, we moved the message up in the GSX menu, so you won't need to enable logging to know there's a problem, and might start looking into it.
I'll clarify again: in MSFS, GSX doesn't have ANY control over jetway, doesn't affect jetways, doesn't move jetways, doesn't control them. The ONLY interaction GSX has with jetways is:
- Make a Simconnect call to know where they are.
- Send the standard key event to toggle them.
When you see the "Bad jetway data", it's JUST the result of the Simconnect call. GSX cannot possibly know WHY the sim said you have bad jetway data on any given airport, that's the only thing we get from the sim, which is a translation for the -99 error that, according to the SDK, means "Internal Error", with no other explanations.
Basically, don't shoot the messenger (GSX).
