FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: aljina on June 22, 2025, 03:35:27 am
-
Since the latest GSX update, I've noticed a consistent issue during landings—right at the moment of touchdown, the sim pauses or stutters for about 1–2 seconds. This wasn't present before the update and makes landings feel less smooth and sometimes harder to control. Version 3.5.7 – June 17th, 2025 States "GSX Pro Change: GSX will restart automatically after takeoff, to reduce the chance that operations performed on departure remaining in a stale state for any reason ,might affect functioning at arrival. "Everything else runs fine. The issue seems isolated to the touchdown moment, almost like a brief freeze.
-
Since the latest GSX update, I've noticed a consistent issue during landings—right at the moment of touchdown, the sim pauses or stutters for about 1–2 seconds. This wasn't present before the update
See a thread from more than a year ago, where some people were also convinced GSX was the cause of the stuttering upon touch down:
https://www.fsdreamteam.com/forum/index.php/topic,30072.msg196719.html#msg196719
As I already replied there, back then, we tried to replicate this without success and:
- It can't be reproduced in any way when selecting a gate after landing, so we surely need way more detail about where this exactly happens and ALL your add-ons, including airplane, AI traffic, utilities, everything, with the precise, exact, specification of the scenery used and if you are using a custom GSX profile, and which one.
- When selecting a gate before landing, the current version doesn't generate objects immediately on touchdown, but it waits for your speed to be below 40 kts so, the stuttering that is normal to be happening when creating the objects at the gate, won't at least affect the actual touchdown.
I'll check again now but, the chance you were referring to, should have further reduced the change this could happen, because a restart after takeoff would prevent that *any* possible background task started by the departure services that for any reason didn't stop, would continue for the whole flight and having some effect on arrival.
That is, unless this change has fixed a case where before, on your system, GSX was ALWASY completely inoperative on arrival (because of an error), but I'm sure if this was the case, you would have noticed, with something like "before the update, GSX never worked on arrival, now it always works but I have stutter on landing", is this what really happened ?
-
Hello! I confirm this problem. If I disable GSX, the freezes disappear.
-
The issue that the original poster described is indeed new and was introduced with the latest GSX update.
In my case, running on a Ryzen 9800X3D, RTX 5090, 64GB CL30 RAM, and full NVMe setup, hardware limitations should be out of the question. I take precautions by creating full physical backups (classic disk clones) before applying major updates, especially knowing how some updates can unexpectedly affect performance.
Interestingly, when I roll back to the previous GSX version using my backup, the touchdown stutters completely disappear—so the link to the latest update seems pretty clear.
-
I just had this issue with the Fenix A320 at Jackson Hole (KJAC, Custom scenery from flightsim to). Did 3 flights in the PMDG 777 before and it did NOT happen there. Destinations were FSDT KIAH, ASOBO KORD & inibuilds KLAX.
All flights with GSX version 3.5.7, downloading 3.5.8 to see if there is any difference. Reporting back.
EDIT: GSX 3.5.8, Fenix A320, KJAC-KSLC (PACSIM) ; Once again short lag right as the wheels touched down. Deactivated GSX before take off at KJAC (so its not popping up with CTRL+SHIFT+F12) and only activated it when stopped at the gate at KSLC.
Can't really tell yet if the lag is coming from GSX or not tho, have to test with more aircrafts and of course without GSX. Any way to completely disable GSX without uninstalling?
-
Also can confirm this has been happening to me since updating my GSX. When I remove GSX the issue is resolved.
-
Okay, the issue seems to be with Couatl64. I had it enabled during takeoff with no issues. However, during landing, there was a 1–2 second pause upon touchdown. When I disable Couatl, there are no pauses and the landing proceeds normally. Update Version 3.5.7–June 17th, 2025 caused it, before this update there were no issues on touch down
-
I am also having this problem since last update. Don't have it with gsx removed.
Thank you,
Anthony
-
I also have this issue since version 3.5.7
Pascal
-
Seen cptCanada said he fixed it messing with GSX but he didn't really say what it was he changed but its for sure GSX.
Thanks,
Dan
-
I always turned off GSX after takeoff to avoid problems during landing, especially in OMDB. But now it is announced that the application will deactivate itself... so what? I caught a stutter today. And also pink textures on the loaders, and when starting to push the IFly 737 MAX jumps with its nose. Definitely worse and worse with each update
-
What's surprising is how support immediately dismisses the possibility that the update might be the cause, insisting instead that it's an old issue from a year ago that was already fixed.
Meanwhile, several users are reporting the same problem, and no one from the team steps in to help. It makes me wonder—has this issue actually reached the right people DEV team?
Honestly, the lack of empathy and professionalism from support is quite disappointing.
-
Yeah I do hope it goes to the devs. When big streamers like cap Canada are saying the product is causing issues, and people in the fourms saying removing gsx fixed that is a sure sign they need to look into it. :'(
-
I confirm that (at least in my case) disabling GSX solves the problem. I have done several flights, always with the same aircraft and under the same conditions, and the only way to fix the pause at the moment of touchdown has been by disabling GSX.
-
Exactly the same every single flight since the update to 3.5.7.....super frustrating
Before this, no issues at all
Now just as I'm in the flare and about to touchdown I get huge stutters/pause
FYI I don't have a gate pre-selected as I'm on Vatsim so I don't gate a gate assignment until I've cleared the active runway
-
Unfortunately same problem here since last update...
Greetings Kai
-
I see the developers don't care at all. No reaction at all.
-
same problem here. I noticed the issue in 3.5.7, updated to 3.5.8 and I still get long pause on touchdown. Removed GSX, problem solved.
-
I see the developers don't care at all. No reaction at all.
You wont get one, they'll just blame the end user as always, I too have been getting these big time recently and today getting the total error and GSX not loading at all, refer to another thread. Have totally disengaged GSX for time being as unusable, lots of people with same issue. Be interesting to see who gets blamed for that one.
-
What's the best way to disable GSX so the stutters on touchdown stop.....without uninstalling the whole thing from my system.
Is it as simple as deactivating it from the universal installer?
Thanks
-
I think just unlink without uninstall will be good enough. I personally uninstalled it because I started getting couatl script errors on launching MSFS2020. I am so tired from all this.... will just fly without GSX
-
What's the best way to disable GSX so the stutters on touchdown stop.....without uninstalling the whole thing from my system.
Is it as simple as deactivating it from the universal installer?
Thanks
Dont deactivate it. It actually deactiveates it from your computer. I made this mistake. Its something that shouldnt be on the menu line to be honest because if you do that you have to re-enter your key etc to reinstall. I think you just uninstall and it unlinks to your community folder (I think).
-
We haven't "dismissed" anything, it's just that, before being SURE of why something happens and what is the real cause, I want to first check all facts first because, even if disabling GSX "fixes" the problem, that doesn't automatically means GSX is the cause.
And no, if I say GSX is not the cause, doesn't mean:
- I'm "blaming users", this is just made up and wrong.
- I'm "dismissing" anything.
When any user reports a problem, it's obviously taken very seriously, so first thing is asking about the situation and trying to replicate it. Somebody reported pauses up to 30 seconds on landing at EGLL with the Fenix, so I tried doing that and, of course, I couldn't replicate it:
https://youtu.be/dLzpXSEuTP0 (https://youtu.be/dLzpXSEuTP0)
This doesn't mean I don't believe it's happening to that user. And it doesn't mean I'm "blaming" the user either. It simply means that: I cannot replicate it. Period. I would like to ask to take this information as VALUABLE information instead of being taken as a "dismissing" or (even more absurd") as a "blame". Because knowing it's not SUPPOSED to happen it's VALUABLE information to understand the real cause behind it and, to see if we can find a WORKAROUND.
So, for the last time, I ask to stop this nonsense that we "blame users" (never happen a single time), or "dismiss" stuff and instead, take the "I can't replicate it" as USEFUL info for you, and also understand why it might not be as easy to "fix" this from our side, without being able to replicate it.
We have been having doing several tests on the GSX community channel on Discord in the last couple of days, and it seemed the problem happened between 3.5.6 and 3.5.7. We made available an Offline installer for 3.5.6 and an Offline installer for 3.5.7, and one affected user confirmed it didn't happen with 3.5.6 but it does with 3.5.7. Remember, we CANNOT REPLICATE ANYTHING, with any version, so I can only rely on reports by affected users.
Somebody hinted it's the Couat64 .exe "because it goes away if I close it". Well, it's not. Because I asked the affected user to keep 3.5.6 installed, but manually replace the latest Couatl64_MSFS.exe from 3.5.8. NO PAUSES so no, it's NOT the .exe either.
It must have been something we did in the actual GSX code, and the only thing that could have possibly have an effect on this, was that in 3.5.7 GSX will automatically restart after takeoff. Which in fact, should be the very thing that should PREVENT this. By restarting on takeoff, we should have removed the risk that something still running or not terminated properly done at departure, could possibly affect the landing, because restarting cleans up everything with nothing from the previous session still running.
This is just a THEORY (because, again, we are proceeding "in the blind" because we CANNOT REPLICATE IT!!) but, if restarting GSX introduces this problem instead of improving, there might be something else going on which we don't know about the simulator, possibly an undiscovered bug or at least a behavior not consistent with how the sim normally behaves. Usually, when a Simconnect client disconnects and restart, everything from the previous session is thrown away: all Simobjects created by it are automatically removed, all data requests are thrown away, all input events are cleared, it's usually a total clean up.
One THEORY is this clean up might not apply to previous requests of airport data, which GSX normally does when flying to know which airports are nearby, so restarting after take off might not have clean up this request (like everything else normally done on restart) and when you land, all requests of airports nearby made during the flight might arrive all at the same time, because usually the only way to cause a pause in the sim is either creating a lot of objects in a very short time OR asking for a lot of data. We don't ask for lots of data, just the list of airport nearby and when you are close to the airport, the data for that single airport you are landing on. This hasn't changed since a very long time, but MAYBE if the issue is the sim doesn't clear up requests for airports in the same way as it clear *everything else* it's possible that a restart on takeoff might have caused this.
So, today there's an hotfix to try ( run CHECK to get it, the version won't change), which a change: now before automatically restarting, a request to remove the subscription to receive data about airports is made explicitly. We don't have any idea if this works because:
- Nowhere in the SDK they ever said you must do that, so we just assumed the standard behavior that every data request is always automatically cleared when a client disconnects.
- We cannot replicate it! So it's really a shot in the dark.
But since the automatic restart on takeoff is the only thing that changed from 3.5.6 to 3.5.7, that's the only thing we can work with.
However, I want to add that things are not THAT SIMPLE, because if you read here on MSFS forum, a user who spent its time to make a PROPER test, with and without GSX, didn't found much difference, but he surely noticed that in ALL cases (even those without GSX!), there are some stuttering on touchdown:
https://forums.flightsimulator.com/t/touch-down-stutters-su16/727324/27
And what about THIS user instead ?
https://forums.flightsimulator.com/t/touch-down-stutters-su16/727324/28
He has freezes on landing, and he use an XBOX so, clearly, not a chance to have GSX there!
As I've said, the issue is way more complex than just saying "it's caused by GSX", I think there are other things going on at the same time, which for some reasons are triggered by GSX, but without being able to replicate it, we can only TRY different solutions and rely on reports by affected users.
So, try the todays' hotfix now, and see if you see any improvement.
-
Good day,
I followed your instructions for the hotfix and ran the check, but I’m still experiencing shuttering. Some users have gone into the Aircraft CFG file, modified the services, and changed the values from 1 to 0 for everything except Jetway — and they no longer experience shutters.
[SERVICES]
FUELTRUCK = 0
BAGGAGE_LOADER = 0
CATERING_TRUCK = 0
BOARDING_RAMP = 0
GROUND_POWER_UNIT = 0
PUSHBACK = 0
SMALL_PUSHBACK = 0
MARSHALLER = 0
JETWAY = 1
-
Did version Version 3.5.7 – June 17th, 2025 have caused this issue
Difficult to say for sure if this is your case. Here's a link for an Offline installer for version 3.5.6
https://app.box.com/s/kymxyazgrs5r0ac98prmtz2alibl26th
Just install this, don't do anything else (don't update), and don't change anything from the previous flight and see if the pause still happens.
-
I'm facing the exact same problem, and it's seriously annoying. It really needs to be fixed.
-
I'm facing the exact same problem, and it's seriously annoying. It really needs to be fixed.
You haven't even read what I just wrote in my last post ?
We cannot replicate it in anyway, and we are trying to GUESS, with the help of affected users, what might be causing it. So, before complaining it hasn't fixed yet, try to understand why it's not so easy to find the real cause and a possible workaround.
-
I followed your directions and installed the offline installer for version 3.5.6. No more shutters—finally, peace of mind. I can enjoy smooth landings again. It's sad that I have to run an older version for the solution to work.
-
From where can you download the old versions?
-
Why delete? I just press "exit" after takeoff, and after landing I start it again
-
It's sad that I have to run an older version for the solution to work.
What makes you think we stopped there ? That was JUST a FIRST step to confirm that, in your case, the old version didn't affect the landing.
If you read my previous post, one THEORY is the automatic restart after takeoff might have caused this. It's only a theory, because as I've said so many times, I cannot reproduce ANY pauses/freezes/stuttering on landing with ANY version, so we can only take guesses, following reports by somebody affected by it.
Assuming the theory the restart caused this is correct, which is difficult to accept for me, because it should prevented it, but that's seems the only change that can possibly be related to entering/exiting airport that happened from 3.5.6 to 3.5.7, there's another fix online now, that has completely disabled it. So try to update again now or, to be 100% sure you have it, download and install the OFFLINE installer again now, and see if the stutters on landing are gone.
- It they are gone, then we can confirm it *was* in fact the restart on takeoff, and all it's fine.
- If they are back again, it means it wasn't the auto-restart, so we are back on square one, so I suggest to keep using 3.5.6 until we find what the real cause was.
-
As I mentioned earlier, version 3.5.6 runs smoothly with no issues related to stuttering. However, after updating to the latest version 3.5.8 (released on June 22nd, 2025), I’m experiencing noticeable 1–2 second pauses or stutters during use. This clearly points to a GSX-related problem, and several other users on the forum have reported experiencing the same issue. S soon as the update came out on the 22 Jun 25. should be looked into urgently.
-
I also downloaded and ran the 3.5.6 offline installer, tested a few times and the touchdown lag is gone.
-
From where can you download the old versions?
https://app.box.com/s/kymxyazgrs5r0ac98prmtz2alibl26th
-
Did version Version 3.5.7 – June 17th, 2025 have caused this issue
Difficult to say for sure if this is your case. Here's a link for an Offline installer for version 3.5.6
https://app.box.com/s/kymxyazgrs5r0ac98prmtz2alibl26th
Just install this, don't do anything else (don't update), and don't change anything from the previous flight and see if the pause still happens.
First of all, I’d like to apologize if my previous comments came across as harsh toward the support team, and I also want to thank you for the updates and the effort you're putting into this.
In an effort to assist—since you're having trouble reproducing the issue on your end—I’m available if you'd like to connect remotely to my machine for analysis.
As mentioned earlier, I don’t experience the issue on version 3.5.6. However, after updating and running even a short flight—like SBSP to SBGR (around 5 minutes)—the problem occurs consistently.
I believe the issue is not related to my system setup. I’m running a clean Windows 10 install dedicated solely to the simulator. My hardware includes a 9800X3D CPU, RTX 5090 GPU, 64GB of DDR5 RAM (6400 CL30), and a 2TB NVMe SSD. I also use Addons Linker to avoid loading unnecessary sceneries and textures. In short, my setup is quite optimized for smooth simulator performance.
I’ll go ahead and install the hotfix and report back to the community whether it resolves the issue on my end.
Fingers crossed that the root cause is found soon!
Update: Tested with the latest version and the issue still persists. I’ll proceed with a rollback to version 3.5.6.
-
How do I properly install version 3.5.6? I ran the offline installer, and the version shows up correctly. However, all ground vehicle models are completely missing, and the service crew is entirely pink?
-
How do I properly install version 3.5.6? I ran the offline installer, and the version shows up correctly. However, all ground vehicle models are completely missing, and the service crew is entirely pink?
Run the online updater again, and then use the Offline installer if it's not fixed. Please don't post about this here, because this thread is very specific to the lag on touchdown.
-
I have exactly the same issues what I already did:
Disable effects
Set settings down
turn photogrammetry off
Turned asobo ground handling off
I just did LCA-AMS and had no stutters after setting GSX back to 3.5.6. It looks like in 3.5.8 it is trying to load services on the airport which cause a freeze of 1 till 5 seconds.
-
Be nice to know if the devs know about this now. It makes GSX pointless being installed.
-
I just got GSX, same issue, how in the world do I get version 3.5.6? Anyone have a link, I don't understand all this offline installer business.
-
I just got GSX, same issue, how in the world do I get version 3.5.6? Anyone have a link, I don't understand all this offline installer business.
https://app.box.com/s/kymxyazgrs5r0ac98prmtz2alibl26th
Just download this file and run it. That's all. You can verify the version later in the FSDT installer and should say 3.5.6 installed, 3.5.8 latest
-
I just got GSX, same issue, how in the world do I get version 3.5.6? Anyone have a link, I don't understand all this offline installer business.
https://app.box.com/s/kymxyazgrs5r0ac98prmtz2alibl26th
Just download this file and run it. That's all. You can verify the version later in the FSDT installer and should say 3.5.6 installed, 3.5.8 latest
Thanks so much :)
-
Add my name to the list. Same issue with pause on touchdown or very close to touchdown.
Oddly, FSLabs control center detects GSX version and tells me it needed updating, so I did.
So if I go back to GSX 3.5.6 does that imply I'll have issues with FSLabs A321?
And why is FSLabs trying to install SODE V1.8.0 from july 2023 when it doesn't work with MSFS 2024 and is NOT needed for MSFS 2024?
-
I get the same issue. Updated to this version a little while ago. My first landing it froze up for about 3-4 seconds, but it was a long flight and thought nothing of it. Then it did it again yesterday, my second flight since the latest GSX update. The game freezes as soon as the main gear hits the runway. Looking for answers, it was then I noticed this issue happening to others. Since going back to the previous version has helped others, I will do the same.
-
HELLO MY DEAR
I came to report how this error occurred to me, and how I resolved it, being 100% sure that it was the GSX that did this to me.
Yesterday I updated my planes, and also the GSX, and was alerted by a friend that this was happening to him, so after updating the entire simulator and addons, I did a small test flight and got the sttuters on touchdown. I decided to do my Friday long haul anyway, and took off in a KLAX-EGLL. Today, the landing was a complete disaster, adding the wonderful gust winds of the MSFS to the sttuter landing.
Thats the live broadcast of the disastrous landing (JUMP TO 24:06):
So, after being extremely upset about this, I came across this post, and decided to revert to the Addon Manager version through the link they sent here. Here's how I did it after this live:
I closed MSFS.
I downloaded and installed Addon Manager 3.5.6.
I just checked the version in the FSDT Installer. (Image in attach)
I opened MSFS and did a EGKK-EGLL, with the same plane, in the same way I did when landing in the live.
And so my dears, here is the result:
I didn't come here to say that GSX did this to everyone, but rather that FOR ME this was the problem, and for now it's solved. If I get stutters on touchdown again I'll come back here to say that I was wrong :)
Link to the older installer (just run and be happy):
https://app.box.com/s/kymxyazgrs5r0ac98prmtz2alibl26th
https://app.box.com/s/kymxyazgrs5r0ac98prmtz2alibl26th
https://app.box.com/s/kymxyazgrs5r0ac98prmtz2alibl26th
-
Downloaded the old version and its now working fine again
-
Going back to 3.5.6 resolved it for me also.
EDIT: the coualt python script error I reported in another thread is also no longer happening with 3.5.6.
Rob
-
I don't know how long do users have to justify that GSX is an issue with Shutters on touch down. Following the most recent update, issues have arisen that appear to be directly related to GSX. After reviewing the update patterns of other major components within the simulator environment, it is evident that GSX is the most frequently updated and likely the source of the problem.
Reasoning:
MSFS 2020 Update Cadence:
Microsoft Flight Simulator 2020 receives official updates approximately once per month, including Nav Data and core sim enhancements. This makes it a relatively stable baseline environment.
Third-Party Aircraft Updates:
Most third-party aircraft developers release updates on average every 1–2 months. These updates are generally well-documented and timed around sim updates or major feature rollouts.
GSX Update Frequency:
GSX, in contrast, pushes updates at a much higher frequency—anywhere from 3 to 5 times per month.. it also increases the risk of issues; example conflicting the shutters on touchdown.
Conclusion:
Given the recent instability and behavior issues observed since the last GSX latest update, and the relatively unchanged state of the simulator and aircraft add-ons, GSX is the most probable cause. rollback of GSX update to 3.5.6 should be considered to confirm to resolve Issue.
-
I can confirm this also
it is not connected to gate selection after landing, it is a new stutter, just before touchdown introduced by the latest update
-
100% same issue for me. Mix of aircraft, worldwide airports, same issue.
-
Same issue here; multi-second stutters w/GSX, no stutters after uninstallation
-
I,m also seeing exactly the same problem since the update, on touchdown the sim freezes for a sec, tried different aircraft and all the same issue
-
Is there a way to rollback or download to 3.5.6? I've had nothing but problems, including the two second pause on touchdown, with the latest release.
-
Confirming that rolling back to 3.5.6 fixed the problem,
Ref developers saying they can,t see the problrms themselves, I have FStraffic and was flying the LV A321, have the developers tried testing for the problem with add-ons running
-
I also was having this issue in MSFS2020, but resolved by rolling back to 3.5.6.
Addons used:
ini A359 and A35K (both with and without ANF zoom on touchdown)
BATC experimental
BATC Traffic Map
LORBY AxisandOhs
Chaseplane
Volanta
Aviaworx Flight Monitor
Navigraph Charts
I only did two landings that had stutters before switching back to 3.5.6 and those airports were inibuilds KLAX (24R) and inibuilds EGLL (27L).
-
Since the last update 3.5.8. I have in a one hour flight like EGSS - EHEH 2 or 3 shutters for about 10 seconds. In that time my FPS=N/A, GCU=0% and CPU=between 19-40%.
Now I did the same flight without GSX and there was no stutter at all. Exept a few 1 second stutters what I have normaly with my system.
By the way, the stutters were in flight, not at landing or take off.
-
And here's one more with the same issue, constant stuttering or rather complete freezes on touchdown. Which can last up to a few seconds. Making landings very challenging to say the least!
How/where can you find previous versions of GSX Pro like the 3.5.6 version people are referring to?
I found a workaround for the iFly 737 MAX8 (for MSFS2020) where I disabled all services but jetways in aircraft.cfg. However, that is nothing but a work-around and based on how the only component recently updated over here is GSX and I never had this issue before, I'd say it's quite clear GSX being the culprit. Regardless what was said in the beginning of this thread where the normal comment was how this is not a problem with GSX but something else.
A comment we've all heard before but I hope for this one, the issue will be properly confirmed and addressed if it hasn't already. Haven't read through all the posts in this thread and possible new comments from the GSX dev team.
-
Just did another flight without any issues, simply by disabling the services in aircraft.cfg for the aircraft you're flying. As long as you keep jetways enabled, I haven't seen any bad side-effect using this method while waiting for Umberto and team to come up with a proper solution.
To me, this is more simple than downloading and installing older versions of GSX.
For anyone else in here having this issue, below is what it looks like over here and working just fine with the latest version of GSX Pro installed. The path to aircraft.cfg in my case is ...\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\ifly-aircraft-737max8\SimObjects\Airplanes\iFly 737-MAX8 but will of course differ depending on aircraft and where you have it installed. This is the MS Store version of MSFS2020.
[SERVICES]
FUELTRUCK = 0
BAGGAGE_LOADER = 0
CATERING_TRUCK = 0
BOARDING_RAMP = 0
GROUND_POWER_UNIT = 0
PUSHBACK = 0
SMALL_PUSHBACK = 0
MARSHALLER = 0
JETWAY = 1
-
My apologies for possibly a stupid question.....but what do I do to get 3.5.6
I've downloaded the file which is now in my downloads folder - it's called Addon Manager 3.5.6 and is 181mb.
Is it as simple as closing the universal updater and then running the downloaded Addon Manager.exe
Or is there something else I'm missing?
I seem to remember I tried to do this a while back for something else and it didn't work.
Many thanks and sorry for the silly question.....just wanted to double check
-
My apologies for possibly a stupid question.....but what do I do to get 3.5.6
I've downloaded the file which is now in my downloads folder - it's called Addon Manager 3.5.6 and is 181mb.
Is it as simple as closing the universal updater and then running the downloaded Addon Manager.exe
Or is there something else I'm missing?
I seem to remember I tried to do this a while back for something else and it didn't work.
Many thanks and sorry for the silly question.....just wanted to double check
Just download it and execute.
-
Just did another flight without any issues, simply by disabling the services in aircraft.cfg for the aircraft you're flying. As long as you keep jetways enabled, I haven't seen any bad side-effect using this method while waiting for Umberto and team to come up with a proper solution.
To me, this is more simple than downloading and installing older versions of GSX.
For anyone else in here having this issue, below is what it looks like over here and working just fine with the latest version of GSX Pro installed. The path to aircraft.cfg in my case is ...\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\ifly-aircraft-737max8\SimObjects\Airplanes\iFly 737-MAX8 but will of course differ depending on aircraft and where you have it installed. This is the MS Store version of MSFS2020.
[SERVICES]
FUELTRUCK = 0
BAGGAGE_LOADER = 0
CATERING_TRUCK = 0
BOARDING_RAMP = 0
GROUND_POWER_UNIT = 0
PUSHBACK = 0
SMALL_PUSHBACK = 0
MARSHALLER = 0
JETWAY = 1
Can confirm this worked for me, thank you!
-
Not sure if I'm doing something wrong, but I uninstalled the new version of GSX, ran the 3.5.6 Addon Manager, and now GSX isn't loading and isn't showing up in my Community folder. The folders are present in the addon manager folder but the links never got created.
-
That's good to hear and hopefully, being able to work around the problem this way can also serve as a hint when Umberto is trying to fix the issue.
-
Yeah i have this issue too.... I'm going to try disabling services to see if that helps, but honestly i can't see that being feasible to do for all the aircraft i have... Might have to rollback to 3.5.6 unless some new hotfix gets posted.
I have a couple of things i want to add though...
First, i want to point out that what i am experiencing is not what i would call "stutters"... This is a flat out sim freeze on touchdown, lasting anywhere from maybe a half second up to something like 5 or 6 seconds depending on the combination of aircraft and airport. This is NOT the same as some occasional performance dips while scenery is loading in a dense area or something that one may occasionally get from time to time if their system is heavily loaded.
Second, for the purposes of helping to reproduce the issue, i would like for the developers to let us know if it would help for us to include not only our system specs and what aircraft/airport we were landing at, but the whole flight plan, how we started the flight (like unloaded at the gate or something), what if any ATC or traffic add-ons we have, and modules that are auto starting in our exe.xml? I don't have a lot of free time to test things too much, but i can certainly provide information if the developers think it would help.
-
First, i want to point out that what i am experiencing is not what i would call "stutters"... This is a flat out sim freeze on touchdown, lasting anywhere from maybe a half second up to something like 5 or 6 seconds depending on the combination of aircraft and airport. This is NOT the same as some occasional performance dips while scenery is loading in a dense area or something that one may occasionally get from time to time if their system is heavily loaded.
this is my exact issue, its almost like right before touchdown the sim hangs trying to load something or restart something. i thought it was one of my other addons until i realized it was gsx causing this issue. now it may not be the soul culprit, but something is definitely making gsx the target for is issue
we will wait and see if Umberto and the team figure out what's the root cause if it's a gsx issue or a sim issue as he stated.
i am curious if there are so many reports of this issue how the team cant reproduce the issue, but i digress
-
i am curious if there are so many reports of this issue how the team cant reproduce the issue, but i digress
If I KNEW why I cannot reproduce it, not only I would found a way to reproduce it, but it would have been fixed long ago. We can only proceed by exclusion, because the ONLY change from 3.5.6 to 3.5.7 was an automatic GSX restart performed after takeoff.
But this has been rolled back, so the current 3.5.8 version which is online now, doesn't do that anymore.
-
So, if I perform a check of my 3.5.8 installation, that should hopefully sort the issue? Meaning I no longer need the "tweak" in aircraft.cfg?
-
So, if I perform a check of my 3.5.8 installation, that should hopefully sort the issue? Meaning I no longer need the "tweak" in aircraft.cfg?
Maybe I wasn't clear enough. I don't have any idea why the problem doesn't happen in 3.5.6, but started in 3.5.7 for some users, because I'm still completely unable to replicate in ANY version, no matter how hard I try ( MSFS 2020, MSFS 2024, different airplanes, different airports, etc. ), and for the same reason I can't guaranteed it would fix it for you.
If you fixed it by disabling the ground services in the aircraft.cfg, seems to indicate it wasn't caused by GSX in your case, because those entries controls only *default* Ground Vehicles, not GSX's, which acts completely independently from those (GSX will work even without those entries).
But again, just try the latest update now.
-
No, you were perfectly clear Umberto but since you said the only difference between 3.5.6 and later versions has now been removed in the latest version of 3.5.8, that would indicate whatever caused the issue as far as GSX goes should no longer be an issue.
I'll give it a go and let you know 👍
-
Hey Captains and Devs. Beside all frustration, i am so thankfull, that you reported the problem here as well and that the older version was posted by virtuali. I have read all your comments and will test tomorrow after my work. Thank you all and be kind.
:)
-
And what is important, i know many of us are using autoFPS tool. It increases or decreases the LOD values during flight. In my example it is at 50 when i am under 1000 feet above the ground.
I shared this information and this thread here, and someone responsed that he was able to fix this stutter by increasing LOD.
Maybe that is something, what could be helpfull to Umberto and Virtuali.
-
So, after my test yesterday with the Services in aircraft.cfg back to normal (enabled) and after doing a check of 3.5.8, I did experience a short freeze again right on touchdown. What was different was how the freeze lasted only for less than a second. Where it before usually lasted for a couple of seconds.
However, what Yoda_1976 mentioned about AutoFPS in combination with GSX might very well be related to what is happening here. I'm also using AutoFPS with the settings seen below for TLOD and OLOD based on altitude. This would also explain why not everyone is seeing this issue as well as why Umberto so far has not been able to repro the issue.
What is still odd though is why this worked fine up to GSX 3.5.6. With Umberto saying the only difference in later versions is an automatic GSX restart performed after takeoff.
Anyway, good thinking Yoda_1976! I do think you have helped narrow down the culprit and hopefully as you say, this will also help Umberto figuring out what is going on here.
These are my settings in AutoFPS if of any help:
(https://i.imgur.com/WVlz2I6.jpg)
-
If you fixed it by disabling the ground services in the aircraft.cfg, seems to indicate it wasn't caused by GSX in your case, because those entries controls only *default* Ground Vehicles, not GSX's, which acts completely independently from those (GSX will work even without those entries).
This is interesting when you say GSX will work without these entries in the aircraft.cfg because when I tried to disable also the jetway service a couple of days ago, GSX thrown me a message telling me passengers stairs could not be found and how I wouldn't see any passengers boarding for this reason.
-
However, what Yoda_1976 mentioned about AutoFPS in combination with GSX might very well be related to what is happening here. I'm also using AutoFPS with the settings seen below for TLOD and OLOD based on altitude. This would also explain why not everyone is seeing this issue as well as why Umberto so far has not been able to repro the issue.
This is in fact interesting. While the AutoLOD can increase fps, the additional handling has a cost, because it might force LODs models already loaded in memory to switch to a different model, and if this happens for a lot of models all the same time, the switching *itself* might cause extra load which will manifest as a stutter.
That's why you might see a benefit by increasing the ranges, you are likely causing less frequent LOD switching and you are also reducing the chance for many LOD switching happening all a the same time.
This part from Yoda_1976 is also interesting:
In my example it is at 50 when i am under 1000 feet above the ground.
1000 feet above ground is an important number for GSX as well. It's the height threshold under which the airport data will be loaded. No matter how big the airport is (but of course the bigger the airport, the more the issue is important) receiving data about the airport is likely the biggest call GSX ever does to Simconnect. Note that, the call from GSX side is very small, what is really big is the ANSWER from the sim, which contains all the data.
If you are landing at a big airport like EGLL and are already inside the airport visibility range (by default 3.0NM), as soon as you pass below 1000 ft, GSX will ask all data for runways, taxiways, parking spots, for the airport. All data that GSX obviously need to work on it. Based on the actual load and the size of the data, the answer from the sim might not come immediately but, what if this big bunch of data is coming exactly at the same time when the AutoLod has also forced LOD switching on many objects because you also crossed that 1000 ft threshold ?
The way Simconnect works, is that if the simulator is busy, Simconnect will be delayed. So what if, if the simulator was busy switching LODs, so it delayed the reply with all that big data about the airport GSX called at the same time of the LOD switch, so it came back *later*, at the worst possible time, that is on touchdown ?
So, you might want to play with AutoFPS settings (or just not start it) and see if it makes any difference.
If this is related, there's not much we can do in GSX to fix it, other than maybe raising the threshold from 1000 ft to something more (it has been like this for a long while).
-
This is all quite interesting and I do think we're onto something here.
What you say doesn't explain though why we only see this after 3.5.6. Because I've been using both GSX and AutoFPS with the same settings for a long time without seeing this problem.
One thing though I'm thinking...could be an update of AutoFPS which actually triggered this problem...?
I do know there's been a couple of AutoFPS updates. Might be worth trying to go back to an older version of AutoFPS and see if that fixes the issue. Will try to find time for that test during what's left of the weekend and will report back.
-
we only see this after 3.5.6. Because I've been using both GSX and AutoFPS with the same settings for a long time without seeing this problem.
Be careful using the "we" in this case.
There's a long discussion on GSX community channel on Discord and, while several users have confirmed that rolling back to 3.5.6 fixed the issue for them, we have also multiple cases of users reporting that rolling back to 3.5.6 didn't make the slightest difference, so that's not valid for everybody affected either.
-
Be careful using the "we" in this case.
There's a long discussion on GSX community channel on Discord and, while several users have confirmed that rolling back to 3.5.6 fixed the issue for them, we have also multiple cases of users reporting that rolling back to 3.5.6 didn't make the slightest difference, so that's not valid for everybody affected either.
Sorry, wasn't aware of that and was only referring to what I've seen in here.
-
Created a thread over in the AutoFPS forum to hear from other AutoFPS users if they are also seeing the same issue and especially those also using GSX Pro.
https://github.com/ResetXPDR/MSFS_AutoFPS/discussions/110
-
Sorry if I ask the most obvious questions:
have you tried disabling the AutoFPS utility and see if it makes any difference ? If it doesn't (or you haven't tried), it might be a bit premature opening a thread on it.
-
Sorry if I ask the most obvious questions:
have you tried disabling the AutoFPS utility and see if it makes any difference ? If it doesn't (or you haven't tried), it might be a bit premature opening a thread on it.
Haven't had a chance yet since this AutoFPS idea was very recently brought up but I'm just about to install the latest version of AutoFPS, released just prior to when this problem seems to have started. If that won't make a difference, I'll try what you suggest and do a flight without AutoFPS.
As for starting the thread and asking if other AutoFPS users see the same issue, I don't find that premature. It's not like I'm pointing my finger, I'm just trying to help isolate the issue by collecting as much information as possible and you're most welcome 😉
-
Just did a test using GSX Pro 3.5.8 with AutoFPS 0.4.4.12 which was released May 30. Which to my knowledge was well before this issue surfaced.
On landing, I once again had a freeze but similar to last flight, the freeze didn't last for like 5+ seconds which I've seen a couple of times before but more about 1 second or even less. More like a severe stutter than a proper freeze.
Another thing I noticed on this last flight was how the overall performance and smoothness in the sim went downhill after I downgraded AutoFPS to this earlier version.
I find that a bit odd since I can't recall having this issue back when this version of AutoFPS was the latest one but instead of pulling my hair and spending too much of my precious spare time messing around with various issues and troubleshooting, I will instead perform a system restore back to where everything was working fine with GSX Pro 3.5.8 and the latest version (0.4.5.1) of AutoFPS and with all services in aircraft.cfg disabled except for jetway. After learning how that one needs to be enabled to avoid messages from GSX Pro telling you how passenger stairs are missing.
Have a nice rest of the weekend everyone!
-
Unfortunately, i do not have AutoFPS. Never have. Yet i also experience the freeze in v3.5.8 (and did in v3.5.7) unless i disable services in the aircraft.cfg.
However, this is the reason i'd asked before if it would be helpful for all of us to post what we have starting up in the exe.xml and how operate the sim, to look for a possible common module loading and also so Umberto can try and replicate the exact scenario we are flying in. Again, let me know if this would be useful.
Also - according to the GSX release notes, didn't the livery manager also debut in v3.5.7? Not saying that's the issue mind you, but the GSX restart doesn't appear to be the only change between v3.5.6 and v3.5.7. What does GSX do or what does the sim do that GSX would care about the instant the sim sees the aircraft changing from flying to landed? That's really the important thing since this happens right when the main landing gear touches the runway.
-
So, after a testflight, same as yesterday. EDDK - EDDP, i can confirm from my side, the stutter or short hang is gone, after installing the 3.5.6 version of GSX Virtuali have shared one or two sides earlier.
If you use autoFPS or not, is not the point maybe. The LOD value in combination with GSX 3.5.7 and 3.5.8 is it. I don`t know what value starts to make problems.
If you are using autoFPS you are able to set it up, how you prefer it. For example, you want to have it at 100 or 150 under 1000 or 2000 feet, you are able to manage it like that. It will smoothly decrease the value that is used at cruise alt for example 200 above 5000 feet. @Virtuali
And even when you not use autoFPS, maybe the LOD value in your case is too low, and the problem shows up.
A guy in the Facebook flightsim group reported, that he has solved it, only by increasing LOD value.
Something between to low LOD and the versions from 3.5.7 seems to be the point. Why? I have no clue. But i was really interested by Virtuali`s posts about this all and how it works.
I will test it the next days, in same config and report back. :)
-
i dont have autofps, just downloaded the newest version of gsx, will report back to see if the issue persists
-
I also do not have autofps. my addons were pmdg738 GSX and FStraffic. I was getting freezing with version 8 and when I rolled back to 6 freezing has gone, so again I say that looking at autofps is not in the equation
-
I am continuing with some testing....
Just did a flight with the PMDG 737-700, i did not disable any services on this plane.
I am still using GSX 3.5.8. I ran the FSDT installer, did an update check on 3.5.8, and it looked like it installed the hotfix.
Ran the sim, did a flight from FeelThere's KSTL to iniBuilds' KMKE...
Got the worst freeze on touchdown i've gotten yet.... I want to say this was almost 10 sec long. On top of that, it looks like COUATL crashed as well (probably due to no response from the sim)..... So that was new..... :)
So, FWIW, the PMDG 737 only has 3 services enabled in the first place - PUSHBACK, MARSHALLER, and JETWAY
We've established that JETWAY isn't the issue. And since the issue happens to me with the PMDG 737 with no changes to the aircraft.cfg, that means it's gotta be connected with PUSHBACK or MARSHALLER.
I was going to turn just one of those off on my next flight that i'm going to do later tonight, but i think i might try a new approach instead. I am going to turn off all the airport ground vehicles in the MSFS settings next and see if that helps....
-
I was going to turn just one of those off on my next flight that i'm going to do later tonight, but i think i might try a new approach instead. I am going to turn off all the airport ground vehicles in the MSFS settings next and see if that helps....
If you disable jetway, that will likely result in the same message I got from GSX, telling me passengers stairs missing and how I won't see passengers boarding. But do let us know. Maybe different depending on what aircraft you're in? I was in the iFly 737 MAX8.
These test results are quite interesting based on what has been said in here up to this point:
- no changes to GSX between 3.5.6 and later other than the automatic restart of GSX
- GSX has nothing to do with the ground services in aircraft.cfg and doesn't need any of them
-
Just an update....
Turning off the ground vehicles in the settings on my next flight did not fix the freeze on landing, nor did turning off ground personnel, which i did on a second flight, but it MIGHT have reduced the length of them... With both flights, the freeze was still there, but maybe only a second in length. Went from iniBuilds KMKE back to FeelThere's KSTL on the first flight, KSTL to Dominic Designs' KBNA for the second one. As always, i rebooted my PC between the flights.
Tomorrow night if i get a chance to do a flight, i'll disable the pushback service only in the aircraft.cfg and see if anything changes. If not, well, then the Marshaller service will be the only one left :)
-
We've established that JETWAY isn't the issue. And since the issue happens to me with the PMDG 737 with no changes to the aircraft.cfg, that means it's gotta be connected with PUSHBACK or MARSHALLER.
Which is interesting because:
- The Jetway is the ONLY default service GSX needs and use.
- The Pushback and Marshaller are the ones which can be disabled and won't affect GSX in any way, since GSX has its own custom versions that don't have the slightest interaction with the default version of such services.
If you had the opposite result (jetway causing the freeze unless disabled), a possible explanation might be that, disabling jetway might reduce the amount of data about the airport being sent back by the sim when GSX asks for it, because *maybe* if you are flying an airplane that has been flagged not using jetways, it might not send data about jetways (even if the real bulk of data is parking and taxiways). But that's not what it seems to be happening.
There's nothing in the returned data about pushback and marshallers, but maybe disabling these would have an effect on how many default ground vehicles/crew are being generated on touchdown ? In theory, this should affect only your airplane, but that pause looked as if the sim was trying to create lots of objects at the same time.
Note that, when I say "GSX asks for it", it means if you are within 3NM of the airport center and you are below 1000 ft above ground. This is the exact moment in time where GSX ask for all data about the airport. However, GSX has NO CONTROL whatsoever about *when* the answer (with the data) will come from the sim. This logic has been the same since GSX came out, no changes ever happened in years.
The only change in version 3.5.7 was an automatic restart after takeoff, this is not done anymore in the current hotfixed 3.5.8. Other changes in the latest 3.5.8 hotfix are:
- GSX is skipping many checks it always did (even long before 3.5.6), like checking parking brakes or engines started, etc. if you are on ground but your speed is > 25 knots.
- Same skipping of unnecessary checks has been extended to when you are not on ground, but your altitude is below 500 ft above ground.
These are NEW optimization we added in the latest two 3.5.8 hotfixes, we never had them before!
So right now, when you are on final or after touchdown, GSX isn't doing anything other than checking your position, altitude and speed to detect when you are again below 25 knots and on ground, so it will start again to check for engines, brakes, to see if you are parked or require a service like the follow me.
If the airport has GSX profile with lots of VGDS (those surely can cause a pause when created and the profile didn't had the "disable static VGDS" option set), GSX will always wait until your speed is below 25 kts before creating those. Same if you pre-select a gate in flight: nothing is ever created unless you landed and your speed drops below 25 kts. this optimization has always been there, and nothing changed either.
What is really worrying, instead, was the report GSX crashed on landing (or likely before). This shouldn't happen, but if it did, an automatic restart will likely cause stuttering, because during a restart there's lots of file access required, so we should probably verify if this was the case.
Checking the auto-restarter log at %APPDATA%\Virtuali\couatl64_boot.log file might tell if there was a restart on (or moments before) landing, since it comes with timestamps.
-
@Virtuali,
so what is the point, that using 3.5.6 stopps the stutter in many cases or increasing TLOD when using 3.5.8?
Something must be there. Or am i wrong?
Best regards
-
so what is the point, that using 3.5.6 stopps the stutter in many cases or increasing TLOD when using 3.5.8?
As I've said, we had reports from several users that even using 3.5.6 didn't fix that, so I think it's must be a coincidence that only worked for some users, because the only meaningful change we had in 3.5.7 was the automatic restart after takeoff, and that is gone in the current version, and we added extra optimization we never had before so, the current hotfixed 3.5.8 has the lightest possible load (as far as communication with Simconnect is involved) on the sim during the landing step we ever had in a long time.
Increasing the LOD seems a more likely explanation but, clearly, it cannot possibly have anything to do with a GSX change or update, since it has no control whatsoever on the LOD switching process, the one and only app that can do that, is AutoFPS, because it access MSFS memory directly.
As I also said in my last post, a GSX restart just before landing might in fact cause this, that's why I provided with information to affected user to verify if this is what happened, by checking the auto-restarter log.
-
I updated again to 3.5.8 and are now on a testflight from EDDK to EDDP. Same as last days. But this time with TLOD 50 in the MSFS settings and without auto FPS. Will report back.
-
Just landed. autoFPS is not used or active. TLOD 50. Stutter is back. Short, under a second, but it is there with latest 3.5.8. It has to do with the TLOD. I am not an expert in terms of software. So i can`t imagine why it is so.
-
I can confirm that I don't use AutoFPS, and my TLOD is always at 150. The only way to correct the stutter for me was to rollback to 3.5.6.
-
I had this issue also and is gone on 3.5.6. However I only noticed it on PMDG planes....3.5.8 didnt give the pause when using the Fenix A320. Can everyone clarify they were using a PMDG product? I used the 737-700/800 when getting the freeze.
*CONFIRMED*
Fenix has NO pause at touchdown on 3.5.8
PMDG HAS large pause at touchdown on 3.5.8
I-fly MAX HAS large pause at touchdown on 3.5.8
Hopefully I havent added mud to water ;D ::)
-
What is really worrying, instead, was the report GSX crashed on landing (or likely before). This shouldn't happen, but if it did, an automatic restart will likely cause stuttering, because during a restart there's lots of file access required, so we should probably verify if this was the case.
Checking the auto-restarter log at %APPDATA%\Virtuali\couatl64_boot.log file might tell if there was a restart on (or moments before) landing, since it comes with timestamps.
Unfortunately, i had done two more flights after the one where Couatl64 crashed, so the couatl64_boot.log file is only showing the most recent flight, where i didn't encounter a crash (just the freeze on landing though it wasn't very long on that flight). There is nothing in there between the messages at 1:02am when i started the sim to 2:57am when i was already at the gate at my arrival (might even be when i exited the sim). If it happens to crash again at landing though, i will be sure to note the time and grab that info out of there.
I had this issue also and is gone on 3.5.6. However I only noticed it on PMDG planes....3.5.8 didnt give the pause when using the Fenix A320. Can everyone clarify they were using a PMDG product? I used the 737-700/800 when getting the freeze.
I have had the freeze with the Fenix A320. To date, i've had it with the Fenix A320, FSS E170/175, iFly 737-MAX8, and the PMDG 737-700/800/900. The length of the freeze has been varying though, anywhere from barely a second to now up to like 10 seconds... I have not tried to roll back to GSX v3.5.6, but i have found, like others here discovered, that changing all services to "0" except for the jetway did clear up the issue completely on the only plane i ended up trying it on (PMDG 737-900). I have no idea about why the length of the freeze varies though; however if Yoda_1976 determined the TLOD can affect the length of the freeze, maybe it has to do with what is visible of the airport at touchdown? That's just a guess though.
Unfortunately, might be a couple of days before i can get back to MSFS, so i won't have anything more to add to this for a bit.
-
Lots of valuable input here now 👍
So far, we have ruled out the issue is caused by AutoFPS or a specific aircraft.
Since the length of the pause/freeze can vary from under a second to well over 10 seconds, it does seem a parameter which can differ is involved. I don't think TLOD nor OLOD are though based on how I've seen the length of the freeze vary even when those values are always the same on touchdown.
-
Fenix has NO pause at touchdown on 3.5.8
PMDG HAS large pause at touchdown on 3.5.8
I-fly MAX HAS large pause at touchdown on 3.5.8
This is very interesting info: we had users reporting freezes up to 30 seconds with the Fenix, so I always tried to use that (assuming it was a worse case), I'll surely try more with PMDG and iFly.
-
Fenix has NO pause at touchdown on 3.5.8
PMDG HAS large pause at touchdown on 3.5.8
I-fly MAX HAS large pause at touchdown on 3.5.8
This is very interesting info: we had users reporting freezes up to 30 seconds with the Fenix, so I always tried to use that (assuming it was a worse case), I'll surely try more with PMDG and iFly.
I have had them in the past on the Fenix, but this was on past iterations of both GSX and the Fenix. Specificly now the freeze does not occur unitil I use I-fly/PMDG aircraft, although the length was different. Ive also set all of them to have services set to 0 in the aircraft.cfg as per above minus the jetway to make it even. But sadly yes Unlinking GSX or Using 3.5.6 get rid of the issue.
-
We are trying a completely different approach here:
- Update GSX to the latest version, 3.5.8
- Remove this folder:
\Addon Manager\MSFS\fsdreamteam-gsx-world-of-jetways\LivingWorld_Config
- Use the free MSFS Layout Generator here to refresh the layout.json for the fsdreamteam-gsx-world-of-jetways package.
https://flightsim.to/file/93859/msfs-layout-generator
- ONLY if you use MSFS 2020: you need to perform an extra step, and it's entering the GSX Config page in the installer, and Disable ALL Airport Services, if you don't do this step, the test is not meaningful.
To confirm the test has been done correctly, you should see the *default* Asobo Pushback when starting on any gate (before you call GSX, after that it will removed).
-
i am also having this issue. except normally about 15 seconds. I downloaded the old version given in this thread, i believe 3.5.6? and it works completely fine again!!! so frustrating
LARGE freezes on the .8 new version - in both the FENIX and PMDG
-
I downloaded the old version given in this thread, i believe 3.5.6? and it works completely fine again!!!
Have you tried the solution I posted above ?
-
I downloaded the old version given in this thread, i believe 3.5.6? and it works completely fine again!!!
Have you tried the solution I posted above ?
Hi, I tested your solution, all was fine, now I see a new version.
What is the procedure with the new build 3.5.9 with MSFS2020. Airport service must be still disable?
Thanks
Christian
-
What is the procedure with the new build 3.5.9 with MSFS2020. Airport service must be still disable?
No, that was just to confirm the problem, now it's all fixed.
-
No, that was just to confirm the problem, now it's all fixed.
So there's now a 3.5.9 where the issue is fixed?
Would be interesting to hear what the true culprit was after all troubleshooting that has been going on here.
-
Would be interesting to hear what the true culprit was after all troubleshooting that has been going on here.
It's right there on the release notes.
It didn't had anything to do with the GSX code, which has always been perfectly fine, it didn't had anything to do with the Couatl engine either. Since lots of affected users confirmed it was fixed by rolling back to 3.5.6 fixed the problem, we have been assuming it was something in the code, the auto-restart, the way the Navdata is received, so we added several small changes trying to make GSX as inactive and lightweight as possible on final and on touchdown, but those didn't do much, because the GSX code never had a problem to begin with!
The problem was the OTHER thing added in 3.5.7, which is the Livery Manager.
It was handling the GSX replacement Pushback for the Asobo model, when it shouldn't have. That vehicle is a bit of a special case, since it has two slightly different variants in the same folder, one user by GSX proper, and one used only as a replacement for the default Asobo tug. The Livery Manager wasn't aware if this special case and it was treating it like any other multi-livery object, so when it was running (it's always started on every update, to resync all operators), it Disabled the Asobo-replacement variant, which is required by the Living World and the AirportServices, in all cases when you don't use GSX.
Apparently, MSFS tries to populate the airport with default ground vehicles when touching down (GSX waits until you slowdown to do that with *its* own vehicles, either when you pre-select a gate in flight or the airport has static VGDS), and the failure to find the object which was disabled by the Livery Manager apparently cause the lag. I have no idea why I was never able to replicate it, maybe it requires a certain amount of installed packages to appear.
Now we separated the "real" GSX pushback from the "Asobo-replacement" variants in two separate folders, and the Livery Manager now knows it shouldn't touch the Asobo variant anymore.
The most englighting post were those from Driver8, who hinted that in fact, the addition of Livery Manager was also something added in 3.5.7, and other reports saying the default Pushback (replaced by GSX, but still a default) disappeared. In fact, the missing default Pushback was the real bug, the touchdown lag was just a side-effect of it.
-
I did check the release notes but wasn't perfectly clear to me what the actual culprit was and how it was addressed.
Great you were able to figure out what was happening and how to fix it in your software to sort the issue 👍
Looking forward to try 3.5.9 out :)
-
Sounds great. Will test it later :)
-
I tested 3.5.9 and the stutter/lag on touchdown is gone. <3
In my case, the performance on ground is not as good, like it was with 3.5.6. Is that possible?
-
Freeze gone here as well using 3.5.9 and didn't notice any difference in performance on the ground.
It was a small airport I flew into tonight though, so if there is a decrease in performance for whatever reason using 3.5.9, it might be more evident at larger and more complex airports.
-
Just landed with the new version and I'm happy to say there was no stutter on touchdown. Worked peerfectly
-
Hi Virtuali,
Just wanted to let you know that the latest update has resolved the issue on my side.
Thank you for the support and quick fix!
Best regards,
-
Awesome news, glad to hear the issue was found and resolved!
I am looking forward to giving 3.5.9 a try, though it probably won't be until Thursday. Based on the reports so far though it sounds like it'lll be smooth sailing :)
-
Should we put our aircraft.cfg files back to how they were now? I know in a few places they said to disable all but jetways under the Services section. I did that with the FSL A321NEO and the iniBuilds A350. It does it not even matter?
-
Not sure if and when those entires are required but mine are back to default now after 3.5.9 was released.
-
You can restore the aircraft.cfg, considering the problem was the default Pushback, it's likely the only setting that used to make any difference before, was the pushback.
-
I can also confirm that after installing the latest update, the mini stuttering that I was getting on touchdown disappeared.
-
Is there something else we need to do besides update to the latest version? editing the aircraft CFGs fixed the issue for me however after updating to the latest version of GSX and using an aircraft with an un-edited aircraft.cfg, I got the 5sec lag on touchdown again. Aircraft was the TFDI MD-11 PW. Landing in KSFO. Was I supposed to do something with the livery manager in GSX after updating?
-
I restored all my settings in both the aircraft.cfg and in the sim to what they were previous to all the testing, updated GSX, rebooted my PC, and now can report that, as expected, i had no freezes at all at touchdown flying back to KSTL from KBNA! I'll continue to do some more flights over the weekend, but from what i can see, i can confirm this is all fixed for me as well. Thanks again!
-
Still getting the stutter with 3.5.9 :(
It's not a multi seconds freeze, its a 0.5-1 sec "lag" but it is still there.
Fortunately I'm able to work around this by editing the aircraft.cfg files. Anything I could have missed after updating? I wonder why it's working for some people...
-
I wonder why it's working for some people...
It's working for ALL people! Not ALL stutters on landing are caused by GSX! On MSFS forum, we read reports of users who didn't had GSX, with somebody even using an XBOX, so clearly he couldn't have had any access to GSX.
GSX 3.5.9 fixed only the case where the stutters on landing were caused by the Livery Manager which disabled the GSX replacement tug for the default Asobo pushback tug: its absence cause that stutter on landing, we could only fix this specific case, because this was the one caused by GSX (or more precisely, the Livery Manager).
If you spawn at a gate without calling GSX, and you see the Pushback tug (it's a GSX model, but it acts as a replacement for default one, so it works from the ATC menu), your GSX is all fine and your touchdown stutters are caused by something else.
-
@Virtuali,
since i upgraded to 3.5.9 i have problems with pink textures. I followed the instructions, uninstalled multiply times and reinstalled. Used Offline installer, new version off Universal installer. Used old Addon Installer 3.5.6 and it does not matter, what version, or if i use the live updater. This textures on the Follow me car stays pink.
Is there something we could do about that? Never experience something like that before.
I even deinstalled/ all folders from the addon manager, temp files and caches. I have no clue what else to do.
Regards Marius
-
I guess i have found a fix. I copied the files for lights and follow me, from the backup cached files for future install and insert it into the right place in the simobjects folder.
It seems to work.
-
I wonder why it's working for some people...
It's working for ALL people! Not ALL stutters on landing are caused by GSX! On MSFS forum, we read reports of users who didn't had GSX, with somebody even using an XBOX, so clearly he couldn't have had any access to GSX.
GSX 3.5.9 fixed only the case where the stutters on landing were caused by the Livery Manager which disabled the GSX replacement tug for the default Asobo pushback tug: its absence cause that stutter on landing, we could only fix this specific case, because this was the one caused by GSX (or more precisely, the Livery Manager).
If you spawn at a gate without calling GSX, and you see the Pushback tug (it's a GSX model, but it acts as a replacement for default one, so it works from the ATC menu), your GSX is all fine and your touchdown stutters are caused by something else.
So i still have the few second stutter/freeze on landing in any aircraft that I haven't edited the .cfg to exclude all services except the Jetway. However in aircraft that I have edited the .cfg to remove the services, no stutter/freeze on landing. What exactly should I look for on load in (in an unedited .cfg aircraft) to confirm that GSX is opperating correctly so as not to cause the stutter/freeze on landing? I want to experiment a bit so I can see why mine doesn't seem to be fixed after the update.
-
Would be interesting to hear what the true culprit was after all troubleshooting that has been going on here.
Disabled the Asobo-replacement variant, which is required by the Living World and the AirportServices, in all cases when you don't use GSX.
Apparently, MSFS tries to populate the airport with default ground vehicles when touching down (GSX waits until you slowdown to do that with *its* own vehicles, either when you pre-select a gate in flight or the airport has static VGDS), and the failure to find the object which was disabled by the Livery Manager apparently cause the lag. I have no idea why I was never able to replicate it, maybe it requires a certain amount of installed packages to appear.
Now we separated the "real" GSX pushback from the "Asobo-replacement" variants in two separate folders, and the Livery Manager now knows it shouldn't touch the Asobo variant anymore.
Which Asobo Package controls the Airport Services by Asobo .... i think about what is "better" -> I generally disable all Asobo Rubbish Packages within the content.xml ... like this fs24-fs-base-genericairports-services or fs24-asobo-apron-control-services
.... Enabling or disabling