just tried live updater and that has worked thank you

 

3 minutes ago, jeff20 said:

thank you for quick reply

yes i was on beta so i tried release channel but still cant update

I had same problem.  Just got it to update by clicking the "Check" button but strangely it is now showing 3.7.2 as installed but 3.7.1 as latest. 

1 hour ago, knich said:

I had same problem.  Just got it to update by clicking the "Check" button but strangely it is now showing 3.7.2 as installed but 3.7.1 as latest. 

That's a problem of the local Cloudflare node in your area, because the installer is being served an older version of the server it hasn't updated. Try using a VPN, or update using the Offline installer.

1 hour ago, virtuali said:

That's a problem of the local Cloudflare node in your area, because the installer is being served an older version of the server it hasn't updated. Try using a VPN, or update using the Offline installer.

Where's the offline installer?

 

24 minutes ago, knich said:

Where's the offline installer?

 

on the fsdt forum under general where all the info you need is there

8 hours ago, PilotPete99 said:

Is GSX compatible with the iFly 737 Max? Apologies in advance if I missed this, as I did not see it listed.

Cheers, Pete

yes it does

5 hours ago, Sonosusto said:

Perspective: for the rest of us it seems GSX has worked fairly well

You seem to believe I'm the only one who has had issues with GSX. That's an interesting take. 

Thanks for this update. The map mode editor is such a quality of life improvement. Very much appreciated. 

15 hours ago, virtuali said:

Support are those "support professionals" that are trained to treat you with courtesy and basically not telling you anything of substance, other than "I'll ask the developer" or "use the system to open a ticket", which are company-speak for "go away, please", but in a way so nice, that you won't even realize they triaged you, because that's their job.

The always-entertaining support offered by one who's job is being a developer and not a real support person, is that you'll always get the blunt, hard and technically undeniable, facts, that sometimes might even be difficult to accept, but in the end you'll walk away having learnt something new about your system and the sim. You'll always get the honest truth here, however unpleasant it might be.

Oh no, don't mistake me. Your "support" is utterly unique and it's rather fun to watch. Never seen anything like it. Please, by all means, continue. 

Nice update and the map thing is really useful. I still find the program very temperamental though - at ini Larnaca last night I just couldn’t get the jetways to respond at all. 

52 minutes ago, bennyboy75 said:

at ini Larnaca last night I just couldn’t get the jetways to respond at all. 

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.

Edited November 23, 2025Nov 23 by virtuali

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... 

So one was a glitch as I expected, but I think others are also seeing the pushback issue with the nose gear...

4 minutes 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... 

So one was a glitch as I expected, but I think others are also seeing the pushback issue with the nose gear...

Probably just run LiveUpdate again as explained by Umberto earlier in the thread:

 

16 hours ago, chapstick said:

You seem to believe I'm the only one who has had issues with GSX. That's an interesting take. 

We're in the same boat, or plane as it were.  GSX has been a net loser for me, and I used it for years in P3D.  After years of dinking around with screwed up initializations of couatl necessitating work around to get the GSX menu to open correctly, numerous odd behaviors including some level of stuttering where GSX actions were the only things stuttering in the display, the solution suggested by Virtuali was to reduce my frame rate to 30FPS because that is an inherent limitation in GSX's use of Simconnect, my plane suddenly spinning 180 degrees during pushback, being pushed back into walls, having ground crew walk thru objects etc etc.  I really want nothing to do with this type of addon requiring installation of airport profiles to deal with these kinds of issues, no thanks, no way.  Were Virtuali to embed proper profiles into GSX instead of adding things like clean up crew and PAX walking into the cabin *(heinous performance impact--immediately disabled here) I'd def reconsider.  I know he's doing the best he can, his priorities just do not align with my own for what matters in moving the product forward, so I uninstalled GSX many moons ago.  I will try it again sometime as I miss a few features of it.  Despite several requests by yours truly to make the dang marshal stop walking all the way to the end of the 100ft straight pushback when I've used the GSX menu to STOP the pushback, the crew continues its 100' march back regardless.  

With the advent of 2024 I have some hope we may see Asobo develop PAX loading at some point since they took the trouble to demonstrate very good looking animated PAX walking down the jetway during the 2024 initialization video and surprise their heads didn't poke thru the roof of the jetway.

I appreciate GSX is a very difficult project to develop but in the end for me it was a net loser, though I do miss a few features of it and will try it again some time.

Edited November 23, 2025Nov 23 by Noel

1 hour ago, SierraDelta said:

Probably just run LiveUpdate again as explained by Umberto earlier in the thread:

 

Ah cheers Soren, I missed that, my mistake so will just run it again after this flight.  

Thank you!

-Paul