Gateway that connect automatically

[Axis360]

Good morning,

I would like to know why at certain airports the gateway connects by itself when I arrive at the gate?
Whereas at other airports, most of the time, it's me who decides to bring it to the plane via the GSX menu.

[virtuali]

Not possible to reply with such a sparse report, missing important things like the airplane used, for example. Some airplanes operate the jetways themselves. And in some cases, the default AI Copilot will do that.

[kingnorris]

Good morning,

I would like to know why at certain airports the gateway connects by itself when I arrive at the gate?
Whereas at other airports, most of the time, it's me who decides to bring it to the plane via the GSX menu.

Happens to me also. I believe if you park perfectly, it'll automatically move. If you're slightly off, it will not. At least, that's what I think.
And Virtuali, I use the PMDG 737-800 every flight.

[Axis360]

I use the fenix A320 on all my flights.
I take an example from the last time in Seville, I arrived, and not even had time to turn off the engines as the gateway came to connect (I deactivated auto jetway in the Fenix ​​EFB) it makes me very rarely.

I don't know if it's the fact that I'm perfectly parked, because I try to be and I think I am every time.

[virtuali]

Maybe I wasn't very clear but, since you are posting here, you might assume GSX has something to do with this. It doesn't: under no circumstances does GSX try to operate jetways automatically. It's always after your command to GSX.

However, as I've said, there might be other cases where the jetway might start on its own, none of these has anything to do with GSX and are:

- The airplane might feature jetway automation on its own.

- The AI Copilot in the sim will sometime operate the jetways. I'm not sure if this can possibly happen under certain condition even if it's disabled.

Regardless of the reason you see jetways moving automatically, it's never GSX. And, just to be even more precise: if you see the airplane door opening automatically when the jetway gets close to it, IT'S NOT GSX either.

GSX **USED** to operate the airplane door when the jetway approached but, since after some update, MSFS itself added this feature with no way to disable it, we removed it from GSX, which will only operate the *other* doors (assuming it can, meaning the airplane either use standard doors or has special GSX integration), but on the main exit (if there's a jetway), because that one is operated by the simulator automatically, when the jetway get close.

[Axis360]

wow! Ok thanks for the explanations! It's technical

[romaf12008]

Ok, is it possible to make sure that if the jetway connects automatically, then after selecting the deboarding option it does not drive away?

[virtuali]

Ok, is it possible to make sure that if the jetway connects automatically, then after selecting the deboarding option it does not drive away?

It surely doesn't, and if you read my previous explanation, it should be clear that, in case that happens, there's nothing we can do to prevent OTHER things to operate the jetway themselves.

[WebMaximus]

Waking this thread up since I have the exact same issue.

Just flew into Seville from MK-Studios for the first time tonight and decided to park at gate 8 which has a jetway. As was explained above, even before reaching the stop position, the jetway started to extend automatically and once I was parked in the correct position, the jetway was now attached to the aircraft. I was in the iFly MAX8.

Figured no harm, I'll just ask for deboarding via the GSX Menu as usual but the moment I did, the jetway started retracting again and I had an aural message from GSX which I didn't hear very clearly but it did mention something about how I wouldn't see any passengers deboarding. Before this message, I also heard something about there were no passengers to deboard.

Would be interesting to know why this is happening because I haven't seen it anywhere else and I do have lots of payware airports and many of them by MK-Studios.

I asked about it over in the iniBuilds support forum as well since that is where I bought the scenery from but thought I would have a look in here as well.

[virtuali]

Following your description, it seems GSX couldn't detect the jetway status, so even if it was attached, it didn't report as such, and this could have been caused by a number of factors, ALL of them of course logged by GSX, that's why you should always try to provide a log when reporting a problem.

Lacking a log, I can only list all possible reasons I can think of:

- There's a scenery conflict, so GSX is getting wrong data about parking and jetways from the Navdata API. Most common cause is not having disabled GSX replacement files for that airport after installing it, but if you have, you might have another scenery in conflict.

- There's a problem with that scenery in particular, like a missing Jetway or an orphaned jetway, and this affects what we receive from GSX.

- The jetway might have "worked" visually, but might have not docked completely, leaving some gap. Normally, when a jetway docks properly, there will be almost zero gap between the jetway end point (which GSX receives from the Navdata API) and the airplane door.

Of course, even when the jetway docks properly, the gap is close to zero, we have a tolerance (50cm I think) to accept the jetway as docked even if it's not fully docked, but it's not as if we can increase it further, because it would be we might start to accept as docked jetways with a gap too wide that might start looking as "passengers in the air", which you might assume it's a "GSX bug", when in fact the problem was the jetway docking partially. This case is not only indicated as a message in GSX, but also logged.

Clearly, if GSX doesn't detect the jetway as docked (again, it's Simconnect that tells us that, assuming we haven't received bogus data about it), it thinks it must dock it, resulting in an undocking, if the jetway is in fact docked.