Thank you for this bug fix. It was driving me mad thinking I was doing something wrong when the jetway was visually connected but I’d get stairs and a bus.
Really enjoying the new KATL but curious why GSX doesn’t have gates T19 - T21 showing in the drop down for Terminal T?
Just completed a flight from LOWW to LOWI on the Fenix A320.
In Vienna we loaded 5 Containers, but to my surprise in Innsbruck bags were unloaded with the conveyor belt.
Maybe a future update can include a logic to ensure that loading and unloading remain the same for a flight.
For now, you can configure your plane in GSX to use only one type of baggage handling system. It would be nice if GSX gets smart enough to recognize the type used for the entire flight.
This has been discussed so many times and, the “realistic” solution is not as simple as it might seem because, in a way or the other, you’ll always end up with something that, for some people, would look wrong. I’ll recap again the explanation that has been provided so many times:
The type of loader can be specified by the aircraft profile or the airport profile so, it’s simply a matter which source GSX should trust more:
- If GSX trusted the aircraft profile, it would make all thousands of existing airport profiles useless. And would clearly look like a bug seeing you change the loader in the airport profile and nothing changed, because the aircraft profile said otherwise.
- So GSX trusts the airport profile, which is what is doing right now, but this would result in what you noticed: different kind of loaders used on arrival than on departure, because the two airport profiles said different things.
In fact, we might say that, in real life, the loaders used are always something LOCAL to the airport, because it’s the airport that has (or hasn’t) the correct equipment to load/unload containers.
What would be the more realistic solution that would match real life entirely ? Something that might still look “wrong” (or a “bug”) especially for beginners, and it would be:
- You started a flight on an airport that was flagged as having ULD loaders, so you load ULDs (unless your aircraft profile said otherwise and the airport wasn’t flagged as NOT having Belt Loaders).
- If you landed on an airport that was flagged as NOT having the equipment required to Unload your cargo, you would be denied from being able to unload it, with some error message saying “Sorry, we don’t have the loader needed to unload your cargo”
That’s the realistic solution, which is still not there. In reality, you won’t even be able to end up in that situation so, if you want to keep it to the extreme realism, you wouldn’t even be allowed to Load on departure something you can’t Unload on arrival, unless you really want to simulate the “passengers landed at KLAX, bags arrived at KSFO” every time the two airport profiles disagree about the available equipment.
But it get better: what if you have an aircraft profile you set up based on airline policy as in “We at Easyjet never use ULDs because they are expensive”, then you plan a flight between two airports that ONLY have ULD loaders ?
See how complex this can easily get ? As in, it’s not as if we haven’t thought about this. It’s because we thought about it that we decided to keep it simple the way it is: just trust the airport and accept what you saw, instead of swamping the user into a draconian (even if “realistic”) bureaucracy about loaders logistic.
Umberto,
I have seen that a new addon to GSX , Cockpit2Ground, has now come out. I wanted to ask if you are ok with it, or do you think they are violating your IP. If you are ok, I think I’ll buy it.
Thanks
We added a complete Remove Control API to GSX to make creation of 3rd party GSX add-ons easier.
… and sorry for this stupid question, but in the future updates, you do not add similar functions from Cockpit2Ground into your GSX ? 
I just ask for a friend
I think it’s very well known we can add any number of functions at any time.
The question was if Cockpit2Ground was “safe” to buy in the relationship with its legality towards our IP, and from that point of view, I could say that yes, there’s nothing to worry about.
Your question is more about Cockpit2Ground possibly become obsolete in the future because we might add its features directly in GSX, and about that, I can only reply with a generic answer that, clearly, any add-on that uses GSX Remote API to control GSX, is doing something that GSX could possibly do by itself in the future, but don’t read that as a purchase suggestion in one way or the other.
A number of posts have been removed. As per the Code of Conduct:
“3rd Party Support/Bug Reporting should be sent to the designated support funnels of each 3rd Party Developer, and should not be conducted in these forums.”
Thank you.
Version 4.0.22 – September 11th, 2026
-
GSX (all versions) NEW: New gate profile option externaljetways = 1 for stands whose jetways are driven by third-party tech GSX cannot detect (such as iniBuilds KORD): boarding and deboarding run simulated at the jetway, without visible passengers, instead of falling back to stairs and bus.
-
GSX (all versions) Fix: “Complete now” while cargo was still being moved made the loader count the unfinished trip as done and call for another train; it now just packs up.
-
GSX (all versions) Fix: A vehicle leaving on a custom path whose first point sat just behind it drove a tight full loop through its own position before setting off - a baggage train doing this appeared to spin on itself.
-
GSX Pro Fix: The cargo staircase platform stopped up to 20 cm above the door at mid-range door heights; it now stops at the door, and all staircases account for the apron slope between the airplane and the stairs.
-
GSX (all versions) Fix: Several issues that could make ground vehicles either wait on each other forever or ignore each other while moving.
-
GSX Pro Fix: In MSFS 2020, the keyboard hotkey could stay inactive for the whole session after a cold start of the simulator, until Couatl was restarted.
-
GSX (all versions) Fix: A departing baggage train blocked by another vehicle now drives around it, instead of asking to remove passenger stairs it only needed to drive past.
Thanks for the external gate fix, as it’s just in time for the new Dubai update from Inibuilds.
I appreciate the effort that you put into GSX, and all the great improvements and features that have been added.
See the latest release notes above a few posts for the fix. Note, this will prevent the bus/stairs from showing, but you will not see any passengers boarding.
It’s not automatic: it must be enabled in the airport profile or using an airport handler.
Because GSX cannot detect iniBuilds custom jetways, it cannot possibly know where they are unless an airport profile specifically made using these non-standard jetways will say so otherwise, how GSX could possibly differentiate it from a real non-jetway equipped apron OR from a gate with a standard jetway that failed to dock (hence the backup bus+stair) ?
That’s just a temporary solution, until iniBuilds would provide us with some kind of API to detect their custom jetways and I already suggested a SDK-standard communication method, but requires work on their side as well, but once that will be in place, jetways (including simultaneous passenger boarding) from iniBuilds could possibly work exactly as the upcoming multi-jetways solution from GSX.
Version 4.0.23 – September 12th, 2026
-
GSX Pro Fix: The TLD staircases could stop up to one meter above the door after the last update.
-
GSX Pro Fix: The CDS staircases stopped a few centimeters above the door at mid-range door heights; they now stop at the door.
-
GSX Pro Fix: The underground refueling manhole could appear misplaced for the whole session when the airplane was automatically repositioned at startup.
-
GSX (all versions) Fix: A door commanded by GSX could be immediately commanded a second time, closing it right after it started to open on airplanes with toggle-operated doors.
-
GSX Pro Fix: On the PMDG 777-200ER and 777-200LR, the front catering command operated door 2R instead of 1R, endlessly opening and closing it while catering waited at door 1R.
doesnt update 4.0.22. I tried both the installer and the live updated.
4.0.22 is the latest version I see in the Universal installer.
Same, no update. Stil 4.0.22
Yes, the update works, and if you ran a CHECK you will get the update.
However, you didn’t see the right version because, even if all files you got are correct and belong to 4.0.23, the manifest.json on the server wasn’t updated, so you didn’t see the new version reported, even if you (if you ran a Check) you already have it.
The issue is fixed now, so you should see the version updated.