Can you give me an example?
All is on ultra, no traffic, running 3440x1400 screen… so what do I reduce?
I’m running a 10900k, 64gb 3600mhz mem and a asus 3090 oC. Asus aio 360 cooler.
Gsync monitor (Alianware curved 3440x1400)
Game mode on, HAGS on, optimized window and dpi settings active.
UPDATE:
I tried to lower the FS settings, even to low settings. But the last core still is at 100%. No matter how I put the settings. How is this possible? Even changing the screen rendering to low does not help.
Friend to change weather to clear skies, last core 100%.
I tried to disable the in data tab online function, still last core 100%.
Tried sr22 tried TbM tried Cessna without glas cockpit, still the same problem.
Tried to start at different locations, still same problem.
Tried to clean the community folder, no solution. Still last core at 100%
Tried to put windows power settings from high to balanced. Still last core at 100%.
Going to try to disable everything, hags, game mode, window and dpi settings. g sync off. Will let you know. For now… I’m lost
You may be right. I had a flight today and the sim was stuttering again. Even worse, I got 2-3fps for a few minutes at crusing altitude. Though, I could swear yesterday was really smooth. One of the worst patches so far, for me at least.
Move your reder scale higher, try 120%, that should force the GPU to do more work masking any stutters. I am not sure why your CPU core is pegged at 100%. It should ideally have 5-10% free fore some kinda leeway. My system is almost the same as yours and my last core has 5-10% free most times.
I disabled game mode, hags gsync. Still 100% on the last core. The only way to free up some cpu room on the last core is to indeed up the render scale to 140/150 or higher. But even then still have the problem with microstutters.
You might want to start by disabling HT first and compare.
You’re screenshot shows clearly the game task scheduler is pinning its main task, the game loop, to the HT CPU of the last core. IIRC when building my own task scheduler, literature was showing you’d rather spawn threads on main CPU core, not on the HT CPU core. In other words, spawn threads on CPU #0, #2, #4 etc…
In your case, CPU #15 is running the game loop and this is the HT CPU (the 2nd one) on the last core, and I believe this is not the optimal way. Otherwise, instead of disabling HT entirely, set process affinity to CPU 0,2,4,6,8,10,12,14
Same for me. CRJ has a little less FPS but much less stutter. Unfortunately the plane is to complex for me at the moment. Lets hope that after the next update the standard planes get fixed the stutter when you are turning on the runway…
On my system this tip seem to work…move the render scale from 100 to 120, the frame rate dropped from 35-40 to 30-35 but with a lot less micro stutters. much better
Do tell how your stutters result in FS2020 being a game. Does this mean that my AMD system, having no stutters makes it a sim? Confused by this particular point stated in your rant. I feel you are comparing apples to oranges.
This render scale increasing from 100 to 120 does not
bring any improvements whatsoever in my system…
As BossMussel37801 rightly writes:
“there’s only ASOBO to stop the stuttering”…
And sarpouli:
" MSFS2020 and stutters ? such an inseparable match"…
There’s not much you can do to fix the stutters. A sizeable portion of the cpu load is probably coming from flight model calculations, cockpit displays, gauges ect. Not much you can do about that.
is this possible, what to do about it?
