Mine’s been much worse today. An interesting departure (SIP1W) out of LPSD - went to external and it looked like the local mountain range was experiencing an earthquake. Rest of flight was uneventful but the landing into Bari was really bad - crosswind & stutters made for an eventful landing in the PMDG 736
Has anyone found this has improved at all. I am still getting performance issues stuttering not all the time but more than I did in SU4 ? Reported to Microsoft but they just blame a mod in their support email.
To me it seems PG related somehow. Yesterday I flew from a non-PG area into a PG area, and that’s also when I started to have some stutters and freezes. Until the PG area it was butter smooth.
As already established by many others, SU4 did not have this issue.
5070 Ti / 64 gb DDR6 / i7-13700
You forgot to include a few key details that actually matter here.
What exact route did you fly - from which airport to which one? Also, which aircraft were you using? That can make a big difference in how the sim behaves.
And one more thing: if your departure airport was a 3rd-party airport, mention that too. That alone can completely skew performance comparisons.
4090, 9800X3D, 64GB Ram, M.2 SSD. Constant stutters in SU5, most evident at low altitude over photogrammetry, exacerbated by aircraft speed - the faster you go, the worse the stutters. A combination of choppy short stutters, several per second, and then slightly longer scenery hitches or rubber banding. All drivers up to date, running 596.49 Nvidia drivers, performed full reinstall of the sim, removal of everything in community folder.
Do the stutters look like the ones from the videos I posted a couple of days ago? I think it was post #160 in this thread.
Same issue with me, consistent stutters of a 1 sec or 2 secs and repeats itself every few seconds.
Sometimes it freezes the whole sim for a few longer seconds and then kicks back in and it just won’t go away! Happens more often after take off when climbing and once it starts, it never goes away until i’m back on the ground.
Yes exactly like your videos. Identical. As you say, TLOD makes no difference. I run on 200, but have tried 100 and 400, it’s all the same.
For me it definitely has something to do with default scenery. As I described earlier in this thread, I can nail down the stutters to exact locations in the sim. Taking off from RWY 31L at KJFK leads to the same stutters exactly at the same points of the runway, I have reproduced it many times. Then continuing into Manhattan leads to manifold stutters across the scenery, all about 1-2 seconds long. It happens with any aircraft, even with all New York scenery uninstalled and photogrammetry turned off. It must be something with the loading of certain default scenery tiles.
I recall a long time ago I had installed a mesh for Scandinavia and each time I reached a certain point when flying across Norway, the Sim started behaving in exactly the same way: Significant stutters about every 3-6 seconds. It only stopped after uninstalling the mesh. Unfortunately, many have now reported to have this kind of a problem with no addons installed.
I once wrote on the forum that flights over Manhattan (KLGA - Manhattan - KLGA) were my go-to test flights and everything was more or less fine. Unfortunately, over time I started noticing that something had changed for the worse. I began getting new stutters that I didn’t have before.
Since then, I haven’t been testing MSFS 2024 by flying over Manhattan or the New York area anymore.
From what I can see, you’re confirming what I noticed a while back when I was testing my new GPU.
Tried this a few days back and it was a stutter fest. Really bad.
After confirming that stuttering occurs at the Handmade Airport, I disabled that feature in the Content.xml file
@CSeiler8351
I found my post from April 16 and I can confirm that something is wrong in the New York area. The performance in MSFS 2024 has gotten worse there.
Again I think we are talking about different problems. The videos in #160 show severe spikes in the mainthread and the frametimes. But there are at least 50 FPS in 2D all the time. BTW the author claims the problems are occurring since release of the FS2024, not since release of SU5.
Others in this thread claim “stutters” beeing 1-2 seconds long - I would call it a freeze.
So this are definitely two different problems.
Could we not just concentrate on reporting the issues and let MS/Asobo decide if it is the same or multiple problems?
I assume they are competent enough to make their conclusion and decide if there is something to address. The absence of “Bug logged” would somehow indicate they do not see any issue as of now.
This permanent “I am right and you are wrong” does not add any value and only make this topic more and more confusing.
One of the goals of such a thread should be to narrow down the issue and identify a workaround or a solution. This will be hard if several problems are mixed up.
We had a similar situation in another thread. There were also more then one issue discussed in one thread. Suddenly the thread got bug-logged and even better, a solution was announced for the next beta release. A lot of people were looking forward to the release - and most of them were disappointed. The bug and the fix was only affecting a few participants, since only one of the discussed issues was fixed. The result were a lot of angry users blaming Asobo for wrong priorities and missing competence. But no one saw their own mistakes, since they mixed up the problems themselves.
Thanks to Raul (FsReborn) for sharing insights. His confirmation of a bug on the base core connects the dots. When a verified developer indicates that the core engine struggles with resource clearing to the point of requiring a complete simulator restart to recover, it strongly suggests a structural root cause rather than individual user configurations. This exact type of fragile memory scheduling seems to be what may choke the mainthread during heavy asset streaming. The wide variety of performance degradation and stutters reported since SU5 seem not to be isolated maintenance issues or individual errors; rather, it appears that different hardware setups and complex add-ons are simply hitting different triggers of the exact same base core bottleneck.
You forgot to include the actual quote and a link to Raul’s (FsReborn) original post.
Apologies for forgetting to include this in my previous post! Here is the direct link to the DevSupport ticket and the exact statements that clarify the situation.
Link: https://devsupport.flightsimulator.com/t/carrer-mode-breaks-sounds-when-plane-purchased/17945
Regarding the root cause, it is confirmed to be an underlying issue: “This seems to be a bug on the base core, I am sure they will fix it quick.” [Raul 2026, DevSupport]
Asobo has provided a specific workaround to resolve it when it occurs: “They are saying when this happens, you restart the sim, come back and everything will be ok. Then, restart the sim and see if you keep the plane and everything works, this is what Asobo is advising.” [Raul 2026, DevSupport ]
Interestingly, the bug does not affect all players equally: “Is odd, because some users are using it on carreer mode withouth isues.” [Raul 2026, DevSupport ]
This should clear up the chain of events and show exactly what is currently advised.