Ha ha… Those Cargo guys just couldn’t be bothered anymore
Moderator edit: Text removed to conform with this section of the Code of Conduct.
Of course not, the offline installer it’s just 400MB, the full install it’s about 15GB, if you do that, you’ll completely break your installation. In fact, this could have happened a while ago but. since several updates, the offline installer will check if you try to do that and will warn about having to complete a full install first.
There’s only ONE reason for the offline installer to exits and only ONE case where you are supposed to use it, and if if you suspect you are not getting the latest version of all files from the normal online installer, which normally always works unless your local CDN node might be outdated.
Now, this used to be more common when we relied on Cloudflare CDN only, and we found that some ISP blocks it (sometimes by mistake, sometimes intentionally) and it’s completely blocked in some countries too.
So, since several releases ago, we moved the crucial files (those that would likely cause errors if not updated) to GitHub instead, so the chance of getting stale files or the CDN completely blocked should be lower now, but GitHub IS still a CDN, so it’s still possible to get stale files, but way less likely than before.
Ok thankyou for clarification.
I only replied about the correct way to use the offline installer, not that it would have fixed that. Yes, it’s a regression added in 4.0.13 and of course will be fixed in the next update.
Version 4.0.14 – August 5th, 2026
-
GSX (all versions) Fix: At a parking where a custom stop position had been saved but the marshaller or docking system itself had never been moved, it faced the wrong way — pointing in the same direction as the parked aircraft instead of towards it, so a marshaller had its back to you as you taxied in. The saved stop position carries a heading of its own, and that heading was being applied to the marshaller or docking system as well. They now face the arriving aircraft correctly, both in the simulator and in the 3D editor. Parkings without a custom stop position, and those where the marshaller or docking system had been positioned by hand, were never affected.
-
GSX (all versions) Fix: GSX could fail to recognise a jetway as connected and would deploy passenger stairs, or board by bus, even though the jetway was docked to the aircraft. Introduced in 4.0.13.
-
GSX (all versions) Fix: Cargo containers could be left standing on the apron instead of being loaded into the aircraft. The loader took the container off its cart before checking that the lifting platform was ready to receive it, and in the cases where it was not, the container was simply set down where it stood. Introduced in 4.0.13.
-
GSX (all versions) Fix: The GPU cart could drive away instead of waiting for its tractor to return, because a successful return was being read as a failure. Introduced in 4.0.13.
-
GSX (all versions) Fix: A jetway that took longer than usual to connect could be abandoned part-way, leaving it attached but not reported as connected. GSX now waits as long as the jetway is still moving, and only gives up if it stops making progress. Introduced in 4.0.13.
-
GSX (all versions) Fix: In rare cases the pushback tug could stay at the nose gear after disconnecting instead of driving back to its parking. Introduced in 4.0.13.
-
GSX (all versions) Fix: Ground vehicles could give up waiting for a vehicle that was still working and drive in on top of it. Waiting for another service to finish is normal — a refuel handled by the aircraft’s own fuel system routinely takes several minutes — and GSX now waits for it properly again. Introduced in 4.0.13.
-
GSX (all versions) Fix: The two de-icing trucks are told to leave one at a time, and if the first one had nowhere to drive to it never reported itself clear, so the second one waited for it indefinitely and the departure could not complete. A truck now reports itself clear whether it drove away or not.
-
GSX (all versions) Fix: If the operator walking to or from a vehicle was removed mid-walk — for example when a service was cancelled at that moment — the vehicle could wait forever for a walk that had already ended, and the service would never continue.
-
GSX (all versions) NEW: Added the following Catering operators: Transpit Catering (Russia).
-
GSX Pro NEW: Added the following Refueling operators: AFSC (Hong Kong), BGS (Baltic States).
Still getting the big with the Fenix especially where the fuel truck won’t leave after finishing which then blocks carts coming to the loaders for the bags/cargo.
Even after selecting abort service it just waits there.
Doesn’t happen here, the truck leaves normally, tested many times with the Fenix, in both situations: when the fuel completes before or after catering (depending on quantity).
Abort also clears everything so no, you must have a problem with the update, try the offline installer.
Also, please don’t reply here since I’ve been asked by the admins to not do any troubleshooting here, maybe report it to the GSX community channel on Discord for a quick answer and a check why it doesn’t work for you.
Version 4.0.15 – August 7th, 2026
-
GSX (all versions) NEW: Custom approach paths — the baggage train’s deboarding role is now authored as two separate paths: Deboard: gate to work for the drive in from its spot at the gate, and Deboard: going home for the trip back out. Keeping them apart lets the trip home use the spawn/despawn at the taxiway entry/exit point option (no taxi-out), which the drive in cannot use, since the train always appears at its own spot at the gate. A deboarding path that already had a Leave route is converted automatically the first time you open that parking’s Paths tab.
-
GSX (all versions) NEW: Custom approach paths — the exit point of a Leave route can now be rotated, and shows a heading pointer of its own. Its heading sets which way the vehicle faces along the last stretch it drives before rejoining the taxiway, and the route preview follows as you turn it. The entry point of an Approach route stays fixed, as its direction is dictated by the taxi route the vehicle arrives on.
-
GSX (all versions) Change: Custom approach paths — route waypoints now use the same numbered markers as the passenger walk-in waypoints, so a route can be read in running order at a glance even when it is not the one being edited.
-
GSX (all versions) Fix: Custom approach paths — the Leave route suggested for the baggage trains bore no relation to the route they actually drive: it was laid out as a straight line back towards the point the train had come in from, which is behind the parked train. The deboarding train and the arriving (boarding) train now start from the train’s own default departure, as every other vehicle already did.
-
GSX (all versions) Fix: Custom approach paths — the entry/exit point of a route moved a couple of metres off the taxiway every time that route was opened and closed in the 3D editor, so the point the vehicle actually taxis to drifted further away with each session. Existing routes are put back onto the taxiway automatically when opened.
-
GSX (all versions) Fix: Custom approach paths — vehicles that appear at their own spot at the gate (baggage trains especially, but also loaders, stairs and the GPU) could be shown at the wrong starting position while their path was edited in 3D, in a different place from one session to the next.
-
GSX (all versions) Fix: The passenger guidance barriers fitted to the stairs could disappear when boarding was requested after a deboarding had already completed at the same stop. Without them, passengers walked straight towards the door instead of following the marked route, which took them underneath the wings.
-
GSX (all versions) Fix: Choosing “Back” on the operator selection page did not cancel the service being requested, as it should have. The service remained shown as requested and could not be cancelled afterwards.
-
GSX (all versions) Fix: A customization saved from the aircraft editor could be written to a different folder than the one GSX reads it back from, so the changes appeared to have been lost. This affected airplanes whose variant is only identified after the profile has already been read, the default Asobo 737 MAX among them. If you have a customization in both places, GSX now reports which one it is using so the unused copy can be merged and removed.
-
GSX (all versions) Fix: PIGS could not be enabled through a gsx.cfg profile on an airplane GSX has no internal profile for, such as one released on the Marketplace only. Enabling PIGS on the two passenger doors now works on those airplanes as well.
-
GSX (all versions) Fix: Ground vehicles that appear at their own spot at the gate — the baggage loaders, the deboarding baggage trains, the passenger stairs and the pushback tug — could turn up a few metres away from the position saved in the vehicle start position editor, and in a different place from one session to the next. GSX was applying a side-by-side spacing rule to them: it exists so that vehicles sharing one remote service parking cannot materialise stacked inside each other, and it was never meant for a position placed by hand. Positions you have set are now always used exactly as saved, while vehicles that really do share a remote parking still spread out as before.
-
GSX (all versions) Fix: The GSX menu could stop opening altogether, with no way back other than restarting. While a service prepares its vehicles GSX hides the menus, and the deboarding service kept them hidden while it waited for the previous service’s baggage loaders to finish driving home — so calling a deboarding shortly after a boarding could leave GSX with no menu at all for as long as that took. The menus now stay available while a service waits for its vehicles, and are restored automatically if a preparation step ever fails to finish.
-
GSX (all versions) Fix: A ground vehicle could become unusable for the rest of the session once it had been dismissed: any service that asked for it afterwards waited for it indefinitely, leaving that service shown as requested with only “Abort” available. The vehicle stayed flagged as shutting down and nothing ever cleared that flag, so it could never be started again. Dismissed vehicles are now properly reset when a service asks for them.
-
GSX (all versions) NEW: Added the following Catering operators: Corinthia (Malta).
-
GSX Pro NEW: Added the following Refueling operators: Enemed (Malta), Harrods Aviation (UK), Signature Aviation (global).
-
GSX (all versions) NEW: Added the following Handling operators: Lufthansa (Germany - updated logo).
Dear GSX makers and community,
just wanted to mention that I really enjoy the growing stability and reliability of GSX. There are still a few hickups, but that is varying on a/c developer and different integration logics. Some of it is still user trial & error, but experience is generally on the upward trend.
For future updates, I would appreciate a much less civilised boarding process: people overtaking each other, rushing up the stairs and clogging the entry door and crowding up the stairs for a while. In sum, the process would be neither faster nor slower, of course, just more childish and pushy. You know, like in real life. I would smugly call this option ‘realisitc boarding’. See the somewhat boring and deeply unrealistic boarding process below (speed setting is ‘insane’).
I’m actually more serious about this than I would like to admit.
Would this be a viable and acceptable change?
Thanks,
Chris
I’d read a lot of the posts above pal, lol. They tell a different story.
I’d take this a bit further. For those flying A32X’s in Spirit liveries, I’d request that GSX provide an update to replicate fist fights in the cabin, passengers screaming and being dragged off the plane by law enforcement. Come on guys, you know we all want to see this!
The update after that will add study-level Waffle Houses to the groundside of the airport…
You can’t call yourself a red-blooded American unless you’ve been to a Waffle House at 3AM.
After that comes a study-level “Carnival Cruise” release.
I kinda thought GSX did this anyway but this seems like a useful free mod?
Anybody else having the engines of the Fenix turn off right as GSX starts up on landing. My last four flights have all had this since the release of SU6.
No! Never had that experience and I fly daily pretty much.
Me too and I can’t figure out what is causing it. It just so happens to be right at the time GSX comes back and right after I turn off the runway. Back to investigating.