Did you mean to reply to me? Sorry I don’t see the connection between our 2 posts 
But I agree, SDE is terrible too. But so are stutters. =(
Have you tried using park control with process lasso? Like in the following video?
I tried out my new Quest Pro earlier and tweaked the settings to hit 72fps, no MR, at 72hz. Wenn it hits a constant 72fps it’s entirely smooth and there are virtually no stutters at all, maybe just the tiniest of microstutters, extremely rarely. So I’m not convinced the stutters are 100% integral to MSFS, at least mine aren’t.
The trade off is of course the reduced image quality and resolution. MSFS has a strange thing going on where upping the resolution (or DLSS quality) increases CPU frametimes, so I’m CPU limited unless I decrease both resolution and LODs. The smoothness is epic though.
Not 100% sure whether I will keep it though. The lenses are amazing but the image quality at 72hz is a big step down from the G2 at high supersampling. Still need to try out dynamic foveated rendering though.
Annoyingly the “smoothness effect” of locking at 45fps at 90hz in the G2 doesn’t seem to exist in the QPro. It’s bearable but not as smooth as in the G2. But the G2 has the intermittent stutters that this thread is (at least partially) about. There’s always something…
EDIT: After some more testing, it seems it’s not as consistently smooth as I thought. Even at a constant 72FPS, sooner or later, you start getting the “rubber banding” stutters, even while at 72fps. So it seems the issue may be with MSFS after all, which of course aligns with the 2D testing that’s been going on in this thread.
It’s similar to with the G2 - there are smooth phases (which at 72fps seem even smoother) but then there are stuttery phases, although they feel a bit different than at 45fps with the G2. Sucks =(. Will probably return the Pro.
1 Like
Why would anything related to the CPU make a difference when the stutters don’t even show up in the CPU frametime graphs?
1 Like
I don’t have the experience, that “Game bar is brutally killing cores”. FSLTL, Fenix and other addons are running on the CCD1 (non 3D cache) core not being killed at all.
Just look at core usage. Some of them are very busy while CCD0 is running MSFS. You could even switch the DOS windows of FSLTL to use CCD0 via Game Bar if you wished to.
And the usage of cutting edge x3D technology with Win 10 also baffles me.
No, I haven’t. This is an interesting idea. As I understand it he enabled Park Control app in Process Lasso, and released Affinity settings, set the game process to High. All this is with Game Mode and Game Bar enabled, I assume, which I have disabled… I can certainly try that.
OK, I’m sold. I will install the Game Bar, enable Game Mode, disable Process Lasso and test without any affinity settings. We’ll see if it helps. Then, as it has been suggested above, I will add Process Lasso but without affinity settings, and enable Park Control addon. See if that gets me any results.
Why? Win11 has a known problem with Reverb G2 - the head tracking becomes to twitchy and oversensitive for many people. Also, it’s just heavier. Win10 is just less clutter and it’s slimmer. Most gamers use it, as Win11 is known to cause stutters etc. in games. I use dual boot - Win11 for work, Win10 for MSFS. Win10 should use 3D cache just as well, if AMD chipset drivers are installed, and Game Bar is installed and running. At least according to AMD. I did test in Win11 and got way worse performance, but my Win11 was not optimized for MSFS. I was checking just in case something in Win10 configuration was causing stutters, but they were only worse in Win11.
1 Like
There are at least 23 posters in this thread, yet the new bug thread only has 10 votes… Come on people, vote if you are affected.
https://forums.flightsimulator.com/t/frequent-scenery-stutters-on-a-top-of-the-line-hardware-with-high-fps-7950x3d-rtx4090-2d-and-vr/
2 Likes
Did you know this (from Tom’s Hardware):
“When you install the Win 10 OS, AMD notes that Windows Virtualization-based security (VBS) may be turned on, but that may mean L3 cache reporting is inaccurate. Microsoft has previously given the green flag to gamers wishing to speed up Windows by disabling VBS (and HVCI), so don’t lose any sleep over disabling this security feature.”
How to turn VBS off:
How to Disable VBS and Speed Up Windows 11 or 10 | Tom’s Hardware (tomshardware.com)
I am starting to wonder what you mean by “stuttering”. 
That performance graph looks great.
BTW, what’s your memory speed and CPU speed?
Yes, the stuttering is not in any way reflected in the graph. If I look at your side while flying low at the moving scenery it’s moving very smoothly but occasionally it “hiccups” or “rubberbands” as if momentarily slows down or freezes and then continues to go. Those are not huge and sometimes can be missed if looking forward. Same thing when doing 360 turns, especially in a photogrammetry area. The turn is very smooth but jitters for a split second sometimes. I.e. the moving scenery is extremely smooth with large CPU and GPU overhead but still glitches occasionally.
6000Mhz CL30 DDR5, and CPU is stock + Curve Optimizer, PBO disabled.
1 Like
Ah, yes. I call this 90 degree lag. This occurs when graphics are moving across the viewport when you look out at 90 degrees from your direction of motion. Those blue runway lights are the worst for this. I have conditioned myself to ignore it because looking straight ahead or out to 45 degrees is smooth.
Interesting that your memory is faster than your CPU speed (Max boost clock) and significantly faster than the base clock speed. Nice rig you have there. Cheers!
That’s one way to call it Although it’s also noticeable in faster turns when looking forwards. It’s difficult not to look sideways when sightseeing, so it’s very noticeable for me.
The consensus is that 6000Mhz DDR5 is the “sweet spot” for AM5 7000 CPUs. Going faster doesn’t yield any significant gains. So that’s what I got. It was a nightmare to make it work at stated XMP speed, but I got it working in the end, and even faster (CL30 instead of XMP CL32). It passes any stress-tests without errors. I did test MSFS with it at stock 4800Mhz too, just in case, but it didn’t help the stutters at all, only the performance tanked a bit.
1 Like
OK, I did test the proper “core parking” with Game Mode + Game Bar + Prefer cores Auto in BIOS. It does work, but it doesn’t cure the stutters. Then I added Process Lasso + it’s ParkControl app to the equation. I didn’t see any significant change. So I went back to BIOS “prefer frequency” + Game Mode off + Game Bar off + Process Lasso setting everything to CCD1 and MSFS to CCD0. It basically performs the same, with no change in stutters. It may give a bit better performance but I have so much overhead it doesn’t matter. Stutters are still there though. It looks like all of that doesn’t matter, along with most MSFS settings. Maybe high LOD and Ultra clouds just may make stutters more frequent, but other than that - same thing, no noticeable effect. I gues I’ll have to get used to it until hopefully there is a fix. Everyone is advised to vote for this bug report so it gets noticed.
It is ridiculous that many people can’t get a completely smooth performance with ultra-high-end systems. It was all about FPS with all other games, which hardware could help with, but here - we have plenty of FPS but it doesn’t help.
1 Like
Is there any improvement with LOD at 50 or lower?
1 Like
As far as I recall, the stutters may be a bit less frequent, but they are still there. Even with photogrammetry off and with the network cable unplugged.
1 Like
I tested this a long time ago on one of the early betas. I had to drop the LOD and resolution down to 1280x720. Not something anyone would want to do for normal flights.
https://forums.flightsimulator.com/t/1-23-11-0-huge-lod-regression/499654/36?u=oldpondgl
I’ve been speculating on this issue for awhile now. The fact that you can get it to disappear should be a big clue as to where the problem lies. You should be able to do the math on this too because I got it to go away by reducing the amount of “stuff” being processed.
MR has improved considerably lately, so I tried it again. With MR set to 1/3 (30fps) and Optical Flow disabled, the artifacts are greatly reduced.
1 Like
Did some more testing with the QPro after yesterday’s initial impression that was very smooth but the stutters reappeared after a while.
Not sure what changed but I have to retract my statement again. Today I did several flights around LOWI and it was super smooth as long as I was able to keep it at exactly 72fps, no stutters to speak off. So now I once again think it’s not an integral game issue after all. I’m very confused.
1 Like
Being confused is the name of the game with trying to find the best MSFS settings. LOWI is not very challenging area. I suggest using KJFK Runsway 31R, take off toward Manhattan and do a few 360 turns over Manhattan, fly low over the skyscrapers a few times. In an airliner or any complicated plane with a speed over 250. Clouds at “scattered”. Whatever settings you set as your normal have to handle that. If they can - everything else should be fine.
1 Like
Broken clouds is better. More taxing on the system…
1 Like