Very nice your long explanation…
But I have tried to download a WHOLE very big region in the manual cache
all three qualities high medium and low, and after disabling the online feature,
tried to fly ONLY in that region. The result is the same: Stutters, no matter what.
Barely OK with the Cessnas, and much worse with all the other planes.
There are simply so many possible points of failure that can happen with complex code and it just strikes me that we can’t rule out that there is something in your local setup that causes your stutters. Just having killer hardware is no guarantee that the components and operating system play together well when hit with complicated programming in a major multi-tasking environment. I just see too many other posts on the forums from people with only marginal systems that seem to be having positive experiences. I had noticeable stutters when I began using MSFS but I don’t now unless I’m in some city where there are literally thousands of buildings and objects that have to be rendered and even then the planes are basically flyable and the graphics stunning. My CPU is not top of the line and I have one of the new 3060ti graphics cards but even before I replaced my old RX580, I had decent flights.
Manual cache is a whole other issue. From what I’ve read we have zero evidence that works at all and could even cause issues. The entry system for it has improved but is still horrible work to set up.
I am not discounting your challenges to Asobo. They should of course be tweaking their graphical engine to get better and better performance but please have some sense of the enormity of the task.
There are at least two distinct reasons for what is generally referred to as “stuttering”.
One has to do with the CPU being temporarily unable to feed data to the GPU fast enough. This shows itself as longer, non-rhythmical pauses. The underlying causes include programs running in the background and delayed data loading from the storage device or the internet.
Another is caused by synchronization problems between the GPU’s frame rendering frequency and the monitor’s ditto. Some call them “micro-stutters”. Often these can be reduced or eliminated via tweaking in-game and/or driver settings.
Personally, I solved the second issue by restricting FPS to 60 in the NVidia drivers, although my G-sync monitor can run at 240Hz.
I rule out that there is something in my local setup that causes stutters based on the
fact that the other simulator, DCS, with a complexity of the planes superior to MSFS
and granted, a lesser complexity of the scenery, runs flawlessly. 60 FPS @ 4k maxed out.
And so do at least a half a dozen games, like for example RDR2, with dozens of NPC’s, light sources,
volumetric clouds.. MSFS stutters even with clear skies, no traffic, and even with the Cessna and lowest settings.
Glat that you are not discounting my challenges to Asobo. They should indeed be tweaking their graphical engine to get far performance…
I do have some sense of the enormity of the task, though other developers had the same task and in my opinion resolved it in a far better way than Asobo…
I forgot…
(To be watched @ 4K 2160P 60. Sorry, a bit long). I have renounced to blend-in an FPS counter, because this is not about FPS, but rather about what a PC Flight Simulator worth of its name should do: Giving the felling of flight trough a fluid movement, and bring correct representations, both visually and technically, of the planes themselves, and the effects that wind, altitude, rain, damage etc. has on said planes. If a photorealistic landscape of the whole world with all the eye candy, giraffes and flamingos included is also possible, welcome, but not necessary. And this as long as it does not negatively impact the fluid movement.
allways the same video.. its a bit borring.. like stutters… 
The only thing that is boring and extremely annoying are the stutters…
And… If you say it is boring…
Here is he Challenge, can you make a video like the - -boring - one I did, and of course with the same 4k quality at 60 FPS, showing that MSFS can run in the same fluid manner as DCS does?
I already did .. but of course I not own a 3080 and so, I can show you ony in MSFS 50 , in DCS 40-60 , in Prepare3D 15-70 and in Xplane 25-60 fps.. sorry for that.
@AC52399 Here is maybe a poor attempt at it but I’d like having your point of view on this one:
NB: there are at least 6 to 8 noticeable stutters in this video but it should be much better now, compared to when this video was taken (thanks to changes in drivers, config, etc…). It runs better now with nearly no stutters on the same computer it was taken (I just didn’t want to take a new video).
I miss the FPS counter 
I have a not listed Prepare3dv5 video.. for relativation a bit
( Heli and Jet with the High-Quality Prepare3d Base Map 
)
@ MichaMMA
Well, interesting your videos, I did not take in consideration Prepar 3D, I had tested it some time ago, and seemed to me a failed try to revamp FSX.. Also Xplane 11 gave me a pretty bad impression, maybe it is a bit better now. Though never as good as DCS….
@ CptLucky8
Your video is a bit short, but you are right, it is a bit better now, hopefully they are making something to avoid those stutters…
Asobo sat themselves the daunting task of modeling the whole world, complete with most of its airports, giraffes and flamingos, instead of dedicating themselves to the very basic, outermost important, essential task which is a proper graphics engine that allows to a fluid movement, thus giving the sensation of flight. It feels like they start building a house from the roof….
(you might want to remove the space " " between @ and the user name so that it registers for notfications)
The video I’ve posted above is in VR at 30Hz (shot through the lens). It just shows what matters for perceiving smoothness and fluidity is not much the fps number, but the constant same fps number whatever the value is.
The problem lies in the fixed display refresh rate and there is no workaround but:
- Displaying images at an integer divisor of the monitor refresh rate (1/1, 1/2, 1/3, 1/4, etc…)
- Varying monitor refresh rate to the display rate (G-Sync, Freesync)
Otherwise you can’t avoid having same rendered image repeating once or more from time to time and breaking the smoothness in the form of a visual stutter.
You might want to try out this: if you know you can render around 40fps more or less and your monitor is 60Hz, try NVidia CPL limiting to 30fps (not in game limiter it is not correctly implemented). If you’re used to 40fps or 50fps you’ll see a difference but overall it will be more fluid. After a while you’ll get used to it (vision/brain).
Now, that is something I could use, CptLucky8. “Vision drain”.
Ha Ha ha
Sorry, couldn’t resist. With your serious response. Apology…
I have an i7 and 1070ti with 16gb ram, I used to get 45 fps easy around the sim with decent settings, even in new york. However, after the last few patches, I can barely get 25 fps consistently anymore. There are massive stutters and framedrops all over the place and at times the sim just locks up for like 10-15 seconds at a time. I tried increasing my rolling cache, then I set it back to default 8gb, I reinstalled my video drivers, nothing works. I can play on the absolute lowest settings, and still get only about 25 fps, and I can also play on the highest settings for my system, 1080p supersampled to 4k, 200% render scaling, and all settings to ultra and still only get 15 fps. This sim is completely broken as of right now for me and its a terrible experience trying to get absorbed with so many stutters and framedrops. As I said, I used to get full 45 on very high settings and easily 60 on medium, but now I cant get it stable to save my life. Frustrating and very disappointing, considering I bought the most expensive version this game along with the eurofighter typhoon and I also bought this game for a friend who was equally frustrated about the game’s awful performance on their high end system. This sucks.
This sucks indeed!
But it is nothing new, they give more importance to the giraffes and flamingos,
than to fix what it is really important in a Fight sim worth of this name…
The only thing that gives me a glimmer of hope is that it seems that they are trying to fix
it, albeit at the moment breaking it even more…
You might be interested in my thread:
i get the same thing , total freezes for 20 to 30 seconds (sometimes longer), and its a total killer of immersion. my processor runs fine and all other programs don’t stop, it’s just MS2020 locks up. Frame rates atrocious at times… 6800K (4GHz) , 2080Ti, 32GB, Samsung Pro SSD M.2, 34" Ultrawide w/G-Sync, GPU never maxed, CPU never maxed. Good VR experience except for these occasional freezes sometimes lasting up to a minute. Unfortunately, no one else gets these freezes, so there’s only the two of us experiencing it. Fat chance it will get fixed.
Take a look at the Windows Error Log for these long pauses. There are timers inside Windows uses to monitor problems with device drivers or services. Drivers and services usually are coded to restart themselves if they crash. It takes some time for a driver to restart after a crash and Windows doesn’t have any visibility into 3rd party drivers and must rely on timers. If a driver can restart after a crash before the timer expires, then normal operation is resumed. During the time from the start of the driver failure to when it recovers the PC freezes because it needs the driver to run. If the Windows timer expires before the driver recovers, Windows assumes the driver has crashed and not restarted. Windows signals to the program, MSFS in this case, that the driver has failed and not recovered causing an immediate CTD.
Sometimes a driver might crash and restart several times in succession before running correctly. Again, if these restarts exceed the Windows timer, a CTD will happen. It is possible to mess around with the Windows timers changing the time from 20 seconds to 3 seconds. This means no more 20-30 second freezes. Instead, a CTD will happen at 3 seconds. This is a lousy choice but no matter what, something is breaking somewhere but in your case restarting. The error log can provide valuable information. If there is a driver that is failing/restarting and is from a 3rd party vendor, you will need to contact that vendor for support. If the driver is from Microsoft, look for an optional Windows Update. Windows usually does not automatically download optional updates.
Ahh, good point. I will indeed do that and hopefully I will find something. I will look specifically at the “Application” Windows logs, thanks for the tip, it’s a good one!
