Doubtful, but Umberto will surely still blame the sim anyways.
This kind of attitude is really not helping anybody, because it mislead users that GSX
might have anything about it so, might no really be a clear documented SU4 Beta bug (this is what it is), but might be instead a matter of personal opinion.
It's NOT.
This is a clearly documented SU4 Beta bug and GSX doesn't have ANYTHING to do with it, because:
- It happens
with an empty Community folder, so no GSX and nothing else active, just default Asobo airports using default Asobo jetways.
- It happens on XBOX as well, so nobody can even try starting an argument like "maybe there's a leftover from GSX even with an empty Community folder". No way GSX would ever ran on XBOX.
- Again, on a empty Community folder on a default airport using default jetways, even the
default ATC menu doesn't recognize the Jetway, as you can see here, when calling Boarding using the DEFAULT ATC Ground services menu, even you can clearly see the Jetway is there,
MSFS is calling a Passenger Bus!GSX is reporting "Bad Jetway data" because that's what is getting from Simconnect. According to the SDK documentation, that's what the 99 error code means:
https://docs.flightsimulator.com/html/Programming_Tools/SimConnect/API_Reference/Facilities/SimConnect_RequestJetwayData.htmIt means "Internal error" so, would you think that GSX should have printed just "Internal error" instead ? Would that be more clear/better ?
As I've said, before a recent update, in order to know you had a problem with Jetways, you had to enable GSX logging and dig into the log to see the 99 error, because if you didn't do that, you would only see the jetway not moving, now it's made more clear with a message that is surely more explicit than the
official "Internal error", so at least you know why the jetway doesn't work.
Because, as mysterious the 99 error code it is, it can happen due to different issues, all of them already known, NONE of them obviously having anything to do with GSX:
1) A very well known bug caused by helipads located very close to a terminal, the jetway would return the 99 error, but only when called from Simconnect, it would still work with the default ATC menu for some reason, so this suggest a bug in the sim Navdata API
2) If there's a "ghost" jetway in the scenery, which means it's a jetway defined in the airport .BGL but not existing in the models library, you'll get a 99 error as well, but the jetway would also be invisible. This error is clearly an airport bug to be fixed by the airport developer but, it's particularly nasty in the way that it affect GSX because, it's enough a SINGLE jetway (not necessarily located in the gate you are in) has this problem, that ALL jetways in the airport queried from Simconnect would fail and return the 99 error, so even jetways that should be working wouldn't.
3) THIS specific SU4-Beta bug, which also reports a 99 error, but in this case the jetways are completely inoperative, in a way that even the DEFAULT ATC thinks there's no jetway there, so it sends a Passengers Bus instead.
ALL these outcomes would cause the 99 Simconnect error, which GSX translates into "Bad Jetway data", because we thought replicating the official "Internal error" from the SDK wasn't very telling.
