Updated without issue, working as expected.  The new editors are excellent… so much easier to manage and setup, great job Umberto.

3 hours ago, psolk said:

So back to report my cleaning crew complete and de-planed using the 777-300 in 2020 however as others have reported I have a new problem I have never had prior with the nose being left in the air after pushback.  I had to hit the brakes and advance throttles a bit to have it slam down... 

That is precisely what happened with the 777-300 only, if the "Pushback raise" was enabled in the previous version and the GSX internal profile had the option enabled only for the -300ER (all the other 777 have it disabled), and it's exactly what we fixed in 3.7.2, the default GSX profile has the option disabled like all the other 777s, so the problem doesn't happen anymore.

Of course, if you customized the airplane with a previous version, the option is still disable, because the GSX internal profile has a lower priority compared to your customizations.

Oh I just had the pushback raise issue with the ifly 737max

3 hours ago, Noel said:

and surprise their heads didn't poke thru the roof of the jetway.

I really must quote this, because it summarize perfectly your complete lack of understanding of GSX and why "issues" happens! This says it all...

OF COURSE Asobo passengers heads don't  poke thru the roof of the jetway, and neither GSX ones do!! They both use ONE jetway model, the default one, where the dimensions (the jetway floor height in this case) are all known and fixed and are all the same for all airports!

GSX passengers " poke thru the roof of the jetway" ONLY at 3rd party airports that can have DIFFERENT models, where the root floor height is DIFFERENT than the default one (most cases it is). Now, while the SDK tells us where the jetway head and where the rotunda is, it doesn't tell us how tall the first part of the corridor is. That is, the floor height at the ROOT of the jetway. That data is just not there.

So to prevent this, we have a parameter that whoever makes a GSX airport profile can use, to give GSX that MISSING information, which is the floor height at the end of start of the jetway, there's a clear example in the manual, with a picture showing passengers at the wrong height to EXPLAIN the problem, and how to solve in, in the only way possible: through an airport profile that would give GSX what's it can't read from the sim.

Edited November 23, 2025Nov 23 by virtuali

@virtuali, I’m surprised to see you on support for FSDT on a Sunday. I’ve posted a request for help on your P3D forum because unless I’m very much mistaken the Live Updater download for P3D has exactly the same number of bytes as the MSFS one.

I can’t get it to run. Early response would be appreciated.

3 hours ago, virtuali said:

I really must quote this, because it summarize perfectly your complete lack of understanding of GSX and why "issues" happens! This says it all...

OF COURSE Asobo passengers heads don't  poke thru the roof of the jetway, and neither GSX ones do!!

That's funny!  You pick the mostly rhetorical element of my comment to respond to.  I understand it full well and was just poking fun on that issue which rarely happened a few times early on. I prefer a bullet-proof, simple solution to loading and pushback and GSX doesn't qualify for that in my many years and versions of experience in using GSX.  What's 'bullet-proof'?  Well, I can manually pushback using built in tools perfectly every time with no need for custom profiles.  I'll take this, automated fully.  YOU don't respond to my comment regarding PROFILES. I want no part of the NEED to install profiles to make PAX loading and pushback function, period, end of story here.   And once more:  the persistent issues with initializing GSX for a very long time was never fixed by the time I uninstalled or put GSX to sleep.   Happened around 15-20% of launches with GSX and I came up with my own solution for when it struck.  And one final time:  years later crew still walks the plane all the way back even when the GSX option to stop the straight pushback length at will is used. FIX these basics before sending out a cleaning crew.  I sent a respectful request to you to address this and got zero response.  Now, you love honesty and bluntness in your responses to others so back at you, minimally filtered.  GSX has no real competition and I know it's near heresy to find fault w/ the source for this, but I welcome something simpler but effective in those domains and I hope Asobo takes it on.  My guess is that the GSX project was likely heinously difficult to adapt given MSFS' limitations so again, love to see Asobo tackle a GSX Lite as it were, amply good enough for my needs.   Some certainly enjoy watching animated PAX walking into the plane etc but I'm focused on all pre-flight checks and is why I'm not missing GSX that much.  When finished with a flight and shut down, my next step is to look for the scoring outcome in SLC, so won't hang around to watch a cleaning crew.  Some apparently welcome all of that and I'm happy for them.

2 hours ago, Noel said:

That's funny!  You pick the mostly rhetorical element of my comment to respond to.

So you admit it was something completely made up, ok. Let's see the others then:

 

2 hours ago, Noel said:

 GSX doesn't qualify for that in my many years and versions of experience in using GSX.  What's 'bullet-proof'?  Well, I can manually pushback using built in tools perfectly every time with no need for custom profiles.  

Another perfect example of self-contradicting statement. OF COURSE you can "manually" pushback with built-in tools, but here is where you missed the point entirely, the whole point of GSX is that you don't have to pushback manually. And if you were happy to pushback manually, why you are even *interested* in GSX in the first place. Clearly, you DO want something that will remove the need to pushback manually, otherwise why spending any time with GSX, if you were happy with doing it manually ?

The automatic pushback in GSX will get you there 90% of the times. An airport profile will reach the remaining ones that cannot be sorted automatically and no, you don't NEED an airport profile.

Have you even heard of the QuickEdit function ? Have you even SAW the new update video, where you can set a QuickEdit pushback in an much easier way on the map ?

 

Quote

I want no part of the NEED to install profiles to make PAX loading and pushback function, period, end of story here

You absolutely donì't need a profile for PAX loading to work, except in a very specific case: WALK-IN gates. If you *want* Walk-in gates, because the real airport has them, then yes, you need a GSX profile and of course, you need GSX, because there's nothing comparable in the sim to walk-in gates.

 

Quote

Happened around 15-20% of launches with GSX and I came up with my own solution for when it struck.  

Of course this doesn't happen anymore, and even when it did happen, it might be maybe 1% of the times. That's the number of times I had to restart the whole sim to replicate it, and find some ways to mitigate what is in fact a problem in the sim sending facility data to GSX, which I think it's solved now.

 

Quote

And one final time:  years later crew still walks the plane all the way back even when the GSX option to stop the straight pushback length at will is used. FIX these basics before sending out a cleaning crew. 

You call this "basics", when  in fact it's a completely minor issue that won't cause any problems other than seeing people walking for too long, on a specific function (Straight pushback), which is likely the least used and, in fact, the one where it might not even make much sense to use GSX.

 

Quote

 I sent a respectful request to you to address this and got zero response.  

Now you are assuming that because you haven't been answered, it means I'm purposely ignoring you. Why not accept the simple fact that I might have MISSED your request ? Happens when you have replied to more than 50K+ message on a forum and 100+ emails every day that something MIGHT be missing. 

 

 

Quote

Some certainly enjoy watching animated PAX walking into the plane etc but I'm focused on all pre-flight checks and is why I'm not missing GSX that much.  When finished with a flight and shut down, my next step is to look for the scoring outcome in SLC, so won't hang around to watch a cleaning crew.  Some apparently welcome all of that and I'm happy for them.

"some" ? Why not saying the vast majority ?

- You don't think we analyze daily sales and correlate the sales surges when some updates (they *always* surge after an update) and you don't think we see which kind of updates drive sales more ?

- You don't think we collect data from various sources to see what people asks ? Because stupid Discord after years doesn't have a feature to sort threads by Upvotes, I had to write a Discord Bot, that reads all the threads, counts the reactions and the votes, and spits that out into an Excel table where we can see what people asked for and voted the most.

You put these together (sales and feedback), and it's clear what people wants, and it's immersion, variety, graphic, eye candy and everything in general related to Boarding Passengers and we are adding new features by religiously respecting user's votes and reactions.

You won't believe which was the update that droves the most sales this year, and it was....THE PIGS! And yes, Cleaning Crew were the previous N.1, now they are done, their spot is taken by "Passengers making queues", that is actually the N.1 most requested feature.

But the MAP is something for those users not too interested in eye-candy, because it makes GSX so much quicker to use, and it completely solved your "I shouldn't need an airport profile to pushback" argument,.

Edited November 24, 2025Nov 24 by virtuali

2 hours ago, Noel said:

I want no part of the NEED to install profiles to make PAX loading and pushback function, period,

Well good thing you don't need profiles.

I note that the entertainment promised in the OP continues unabated.  I also wonder with some amusement why devoting resources to adding cleaning crews was thought to be a priority.  But that is just me no doubt there will be appreciation from some.  The other updates look more promising but I have yet to figure out how to implement them.

Bruce

2 hours ago, virtuali said:

You won't believe which was the update that droves the most sales this year, and it was....THE PIGS!

This is the thread that keeps on giving…. Brilliant!

No disrespect intended at all to you @virtuali.. just enjoying these extremely passionate discussions. 

Keep it coming Umberto, appreciate your work and dedication.  Path finding is VERY difficult, especially where there is minimal SDK support.

I have been trying to update GSX since early Saturday morning. Even this morning (Monday) it is still telling me that I cannot, as Maintenance is being done on the web site. 

Must be one heck of an update.

20 hours ago, virtuali said:

Yes, one of the most common misconceptions is that GSX has anything to do with the fact that jetways works or not. I guess this might be related to the way it was in FSX/P3D, where GSX has an almost full control of jetways. "Almost", because the real background job was made by SODE, GSX simply integrated it. But there, the default system was completely bypassed.

In MSFS, jetways are completely in control by the simulator, GSX doesn't do anything to control them, other than sending the standard "TOGGLE JETWAY" event you could have send yourself using something like Mobiflight, for example.

That's all GSX does to "control" jetways (=nothing). If they work (or not), it's always a combination between:

- how jetways are modeled and placed in the scenery

- how the airplane is parked in relationship to the jetway

GSX only asks Simconnect where the jetway are, and if they connected. If they fail, GSX has *nothing* to do with it, other than reporting it. If you see the "bad jetway data", it's because GSX got a 99 "Panic error" from Simconnect, which we translated in a more user friendly "bad jetway data", but fact GSX reported that, it's not a result of its failure to operate jetway (you can't really fail to send a "TOGGLE JETWAY" event), it's just a *report* of the result Simconnect reported back to GSX, on the connection process GSX has *NO* control whatsoever.

Basically, don't shoot the messenger.

And yes, there's a known bug that heliports close to a terminal would cause jetways there to malfunction, the only solution is to disable the airport with a custom .bgl file, we had to do it for our KORD airport, because an heliport close to Terminal M made all jetways there inoperative and the tricky thing is, those jetways would continue to work using the standard ATC menu: they only stopped working when toggled with the event, and I can understand how users could be *misled* assuming it as a "GSX bug" ( "they work from the ATC menu, it must be a GSX bug!!"), because the way the bug manifests itself, but the REAL bug is the conflict caused by the nearby heliport, because after we found the real cause, we added the heliport exclusion to KORD and the problem was gone, and jetways at Terminal M immediately started to work again with GSX.

So, whenever you see something that you might *think* it's a "GSX bug", think again, because most of the time, the real issues is not as it seems.

Appreciate the explanation and I now see that jetways work differently in 2024. Thanks for your hard work and continuous updates to this software, it’s indispensable for me and many others I’m sure. 

5 hours ago, IanHarrison said:

I have been trying to update GSX since early Saturday morning. Even this morning (Monday) it is still telling me that I cannot, as Maintenance is being done on the web site. 

Must be one heck of an update.

If this is using the “Universal Installer” then it confirms the problem lies at the FSDT end and not on our local PCs.

I downloaded the Universal Installer yesterday on their P3D link but it runs briefly before exiting with no advisory message.

The links to Release Notes for GSX here are broken too.

Has anyone managed to successfully run Live Update for either sim?

The absence of Umberto on the support forum suggests he’s investigating the problem which will hopefully be fixed because as things stand I have no access to either GSX or my FSDT airports as the crucial couatl64.dll is crashing.

59 minutes ago, Ray Proudfoot said:

If this is using the “Universal Installer” then it confirms the problem lies at the FSDT end and not on our local PCs.

The problem is NEITHER your local PC NOR our installer or our server. Nobody connects to our server, you all connect to various Cloudflare nodes depending on your area

If you see the "In maintenance" note, or you see a version number lower than it should be (like 3.7.1, which doesn't exists anywhere on our server), it means your local Cloudflare node is not updated, which of course is not normal, but sometimes it happens and it fixes itself in a couple of days. The maintenance mode was active for less than an hour the day the update came out.

The solutions are always the same, suggested so many times on our forum:

- Try using a VPN to update

OR

- Try using the Offline Installer, linked in many places on our site: the Home page, a Sticky thread on the forum and the products download page

OR

- Be sure you haven't selected the Beta channel. The update is released and we haven't had a Beta in a long time, so if you are still on the Beta channel, switch to release

 

Yes, the release notes link is broken, but it has *nothing* to do with your issue, and will of course fixed.

Edited November 24, 2025Nov 24 by virtuali