I’ve been doing a bunch of tests with CapFrameX lately, changing what seems like every possible variable other than the sim graphics settings I’ve settled on (Live weather, PG on, mix of Ultra/High, 4K DLSS Quality, TLOD/OLOD both set to 150.)
Here’s what I’ve settled on (edited)
nVidia Profile Inspector (disabled)
nVidia App (enabled, optimized for baseline, but tweaked a bit.)
HAGS On
VRR On in Windows and OFF in the monitor settings.
Rbar Enabled in BIOS
Frame Gen OFF
Framerate Cap OFF
Vsync ON in sim (100% Monitor Refresh Rate)
Gsync OFF
Monitor refresh 144Hz
GPU driver 581.29
Game Mode OFF
Power profile Bitsum Ultimate
Bitsum Core Parking (disable core parking.)
Process Lasso using custom affinities and priorities.
Afterburner GPU undervolt mild curve with 106% power limit and a slight frequency boost.
PBO undervolt @ -10 offset (all cores)
I also use POPM, ReShade, FSRealistic, and FSLTL.
The best I can do sitting at a KSEZ ramp in the Sting S4 is a smooth, steady 46 FPS with very minimal interframe latency.
Disabling Process Lasso caused the sim to run on my CCD1 (non-Vcores 30% utilization) instead of CCD0 (vCores 3% utilization) That’s weird, since before SU3 I didn’t see that behavior. I suspect something else is going on, and I need to investigate. Perhaps a recent BIOS update reset X3D Turbo Mode.
ETA: The BIOS update did indeed re-enable X3D Turbo Mode, which basically disables one of the two CCD’s on my 7950X3D. That’s got to be why the sim only ran on CCD1 when Lasso was disabled.
I also found that using FSR3 Frame Gen caused my interframe latency to skyrocket. I think that’s much more important than overall framerate. Perhaps if I upgrade to a 40xx or 50xx GPU and use DLSS Frame Gen that might improve. But with my 3090 Ti it’s not an option, and FSR3 Frame Gen is off the table for now.
Congratulations on this research and optimization work.
A point of attention: check the GSync operating range of your screen. Many models have a GSync range that starts at 48hz. At 46 fps, you are outside the range, so logically GSync is inoperative. If so, try to gain a few more fps.
This is partly why framegens are so important in MSFS 2024: without them, many PCs would not even be able to reach and stay in the GSync range of their screen, resulting in tearing and stuttering.
Most of the settings I’ve been testing are things you could (maybe should?) be testing on your system.
Notable exceptions are Process Lasso and Windows Game Mode.
When correctly tuned, Process Lasso is very beneficial for dual-CCD CPU’s like my 7950X3D.
I see little benefit to using it on a single-CCD CPU like your 9800X3D.
One of the things Lasso does is manage core scheduling (in a number of ways) but if you aren’t using Lasso, Windows Game Mode should be handling that function.
Also, I’ve heard others here says that the 9xxx-series CPU’s are better optimized with Game Mode than 7xxx-series. It would be a good idea for you to test that feature regardless.
I think one of your takeaways from the info I posted above is: 60 FPS is not a failure. I have a pretty powerful system, and 48 FPS is what I get with a fairly demanding set of things at play. Flights are very smooth and stable, and that’s WAY more important than just FPS.
Oh yeah seen that before, perhaps I will try TAA again see if that has an effect, just really trying to see what effect settings have more than anything.
Maybe increasing buildings, grass, rocks e.g also taxes the GPU more,
I’ve found that DLSS DLAA looks better than TAA, and taxes my system about the same. My system isn’t quite up to either one with a mix of Ultra/High settings, and is a lot better with DLSS Quality.
I remember seeing a post of yours saying you was more GPU limited, have you settled on any settings yet, what are your main settings and nvidia control panel settings if you have please?
I find this sim really odd sometimes yesterday I had a good flight, nice and smooth today I go on it and I get lots of micro stutters! I’m still on SU3 here, not tried su4 beta yet.
I’ll post screenshots for you. Probably be Tuesday before I can get to it. But here are some CapFrameX tests I did with the general settings I posted above.
I can’t explain the results shown on the bottom picture. I captured that one on approach/ landing/ taxi into KLAS (which has always been problematic for me.) It looks like a stutter-fest, right? Nope. It was smooth as silk, with a little bit of ‘object popping’ on approach - not enough to bother me.
I did notice during the flight that Dev Mode was showing me a little more “Limited By Main Thread” but yeah, I’m still GPU limited overall. During this test I was seeing:
CPU Utilization around 35% (temps around 55°C)
GPU Utilization around 98% (temps around 65°C)
I took your adice and upgraded my PC to a MSI x870E Carbon MB. I also put in an NMVe card and 64GB RAM (2x32GB). I put in a 1000W psu. AMD 7 9800x3D and 5080 are original to previous PC.
I am now on my 2nd test flight, 1 with a 172 and this one with Beech C90. Both over an hour but at low alts and to low impact airports. I am happy to say no problems anymore and as you can see on the newest Nvidia driver. Since it came back from the original builders and updaters I have only increased LOD/OLOD to 200. I am so happy!! (Admittedly at the moment no complex flight plans or routes - thats to come though in further tests)
I do not. No cap anywhere - not the sim, not NVCP, not FSync, not RTSS.
I’ve done a lot of testing with CapFrameX (which I highly recommend when tuning different settings) and my system seems to run best when it’s free to render as many FPS as it can.
Logically it makes sense to have one. It just isn’t testing out that way - for me. YMMV.
Just be forewarned that a number of WASM aircraft are having issues with SU4 through the first couple builds and may not work properly or at all until Asobo corrects whatever regressions crept in.
I tried your settings a little while ago, very smooth and looked great, was getting low/mid 60s in the A2A Comanche with your settings, only thing different was I had buildings on Ultra.
I got a micro stutter during landing into Santander (LEXJ), other than generally really good.
