FSDreamTeam GSX for MSFS

Version 3.5.8 – June 22nd, 2025

  • GSX (FSX/P3D) Fix: SODE Jetways at 3rd party airports detected as standard.

  • GSX (FSX/P3D) Fix: Some FSDT airports not showing the complete list of gates.

  • GSX (all versions) Fix: Removed Tasklets timeout check from the Python 3 engine.

  • GSX Pro Fix: Baggage loader crew showing pink textures after reducing the operators through the Livery Manager.

7 Likes

@Umberto67 Can you figure out why I’m experiencing this issue? There’s a whole thread on it. It only started recently, before last week it was all fine. Touch Down Stutters SU16 - #13 by davegranstrom16

I didn’t find anything of value in this thread on your forum either: GSX Causes Touchdown Stutter

Hmmm… I’ve recently noticed a 3-5 second pause in the sim (FS2020) when I touch down. Not really a stutter, but is that consistent with what you’re seeing?

(Maybe later this week I’ll try some FSPanel landings with GSX running and not running and see if I can draw some correlations.)

1 Like

If you kill Couatl before landing it will still freeze. To eliminate the pause, the GSX shortcuts must be deleted from your Community folder. To reinstall it, just relink GSX in the FSDT Installer.

I tested everything I had recently added, but it was all the same. GSX was the culprit. Must be something in the latest update.

1 Like

We have been investigating this issue, and at this time is not clear why it happens only to some users.

I cannot replicate it in any way, but tests by affected users has shown the problem must have happened between version 3.5.6 to 3.5.7, and the only change that can possibly have some distant relationship to this, is that in 3.5.7, the Couatl engine is automatically restarted after takeoff, and if you followed the thread on GSX Community server on Discord, there’s a way to disable this behavior but right now, I’m still waiting reports from affected users if this fixes it, because until now it’s just a theory, which I cannot verify because I cannot replicate it: I have 100% smooth landings even at the most demanding airports (EGLL landing with the Fenix).

Keep saying this is just a theory until reports from affected users are coming in, one would think that restarting the Couatl engine after takeoff should prevent exactly that, because it would eliminate the slightest chance that any possible background task performed at departure would affect the landing, so you’d expect restarting after takeoff should fix that, not causing it.

I suggest everybody affected to report it in the appropriate thread in the GSX Community server on Discord, where there has been several troubleshooting steps that has been suggested.

OK, I was testing at FlyTampa’s KBOS in the Fenix if you want to try that, but it was evidently clear that GSX was in fact causing the issue, of that there’s no doubt. Perhaps something changed recently, i.e. GSX is placing objects on the ground just after I touch the ground (as was mentioned in this thread GSX Causes Touchdown Stutter) and that is why I’m experiencing this pause? Is there some sort of setting I can use to disable all ground equipment within GSX? Then I can test it again and see if that fixes it.

I was not aware there is a v3.5.7, on my FSDT Installer (beta channel) it says 3.5.6 is the latest.

Should I switch back to the full release? It says the latest version there is v3.5.8

Have you read what I just wrote ? It seems to be isolated in a change in GSX 3.5.6->3.5.7 but, I think to have explained quite clearly the ONLY “change” happened in GSX, which is an automatic restart after takeoff, which should have in theory prevented this, not causing it.

Also, you know very well there’s another thread here about a pause on landing, because you posted on it and:

  • How do you explain more than a user confirming he has the freeze on landing WITHOUT GSX ?
  • How do you explain a user making a precise test with and without GSX with an actual frame times, not finding any differences between with or without GSX, and showing there IS something slowing down at touchdown ?
  • How do you explain an XBOX user having this issue ?

That’s just to say, before saying it’s “evidently clear” that GSX was in fact “causing” the issue, it’s best to find the real cause, because it might be just a side effect happening because GSX is doing something slightly different (to prevent it!), that doesn’t mean GSX is the “cause”, if it was the only cause, it would happen to everybody using GSX (it doesn’t) and it wouldn’t happen to somebody not using GSX (it does).

If you are having this issue with 3.5.6, you would be the first and only saying it happens with GSX 3.5.6, because all (limited) evidence we got so far, according to other affected users, is that it started happening only with 3.5.7, and we made a couple of test to confirm that.

ALL of these test, made by affected users because, as of now, I cannot reproduce it in any way.

In any case yes, it would be best if you switch off from the Beta channel. The Beta channel is completely empty, and there’s no version 3.5.6 available anywhere on our site, what you see is a trick played on you by your local cloudfare node showing a version that doesn’t exists anymore on the beta domain that is just empty right now.

But as I’ve said, this is NOT the place to do proper troubleshooting, so I’ll repeat it again: everybody affected should report it in the appropriate thread in the GSX Community server on Discord, where there has been several troubleshooting steps that has been suggested.

Gotcha. I can’t speak for others, since MSFS and all it’s issues differ majorly from one system to the next, but for me personally, GSX is obviously the issue. I will try switching to the full release channel and test again. Thank you for your answer!

I uploaded two videos of the problem.

Can you post that here? I’m not interested in browsing endless pages of Discord to find it.

Feel lucky you don’t have to go through 133 pages of the GSX manual without any index or bookmarks.

1 Like

Yes, I’ve always found this to be strange. I’ve never seen a manual without at least a table of contents.

2 Likes

I’d tend to agree with you gentlemen, but have realised that this is old fashioned thinking in an age where you can simply search for any given term when looking at a PDF manual such as this.

@Umberto67 Well, after more testing this weekend, I think I found the cause of the problem within GSX. You mentioned that GSX restarts the COUATL engine after takeoff. Well, it seems that the app only regains functionality upon landing. That is the pause I’m seeing.

If I manually restart the COUATL engine after takeoff, and then relaunch the GSX menu inside the sim before landing, I don’t get the pause on touchdown.

This should get investigated further. Since it only started after the update that made COUATL restart after takeoff, so it’s most likely related to that.

1 Like

Great detective work, Dave! I’ve had the touchdown pause quite a few times this last week. I’ll independently see if your workaround fixes it for me.

1 Like

This should get investigated further. Since it only started after the update that made COUATL restart after takeoff, so it’s most likely related to that.

If you followed the relevant thread about this on GSX community channel on Discord, you would have known this was suspected to be a possible cause and because of this, since several days, the latest version available online has the auto-restart after takeoff disabled

2 Likes

And that version is 3.5.8?

Yes, but always perform a CHECK to get the latest hotfixes (they have been up for a few days), because during the various tests, the version number hasn’t increased.

OK. I see you are aware of the problem, and are working to fix it, so I am going to stop testing and get back to flying. Thank you for your answers and I hope this gets fixed soon.

Version 3.5.9 – July 8th, 2025

  • GSX Pro New: PIGS (Passenger Integrated Guidance System) added to selected airplanes when Boarding/Deboarding with Stairs. Currently supported airplanes are: Microsoft A310/A320/A330, Fenix A319/A320/A321, FsLabs A321, Asobo 737 Max, iFly 737 Max, PMDG 737-600/700/800/900, iniBuilds A300, Leonardo MD8x.

IMPORTANT: The PIGS function assumes the airplane doors to be set in the same position as the default GSX Internal profile. If they have been customized by moving/rotating doors, the band won’t connect precisely. If any doors are removed, the PIGS might not appear. Future updates might include an editor to fix these issues and configure the system with any airplane.

  • Livery Manager Fix: The Livery Manager won’t handle the Pushback used to replace the default model on Living World or Airport Services anymore, which caused its disappearance when calling Pushback using the ATC Menu and, in some cases, a lag on touchdown, due to MSFS trying to populate the airport with a missing vehicle.

  • GSX Pro Fix: Wrong material in the Cargo Driver character N.02, causing rendering artifacts on his face.

  • GSX Pro Fix: Fixed skinned animation on “Emma” Marshaller, in summer clothing.

  • GSX Pro Fix: Menu stuck on Loading in MSFS 2020 when starting from the Main Menu for the first time.

  • GSX Pro Fix: GSX won’t assume the airplane is on ground anymore if it’s frozen using the standard SimVars. Instead, it will check its own LVar, so it will consider the airplane to be on ground only if the freeze was initiated by GSX (airplane raised during Pushback). This should prevent conflicts with other add-ons that might also freeze the airplane for any reason, unrelated to Pushback.

  • GSX (all versions) Change: The log files now have timestamps, for easier debugging.

9 Likes