I ran into this little tidbit again today, so thought I would bring it to the attention of the masses, either as a heads-up for the new crowd, or as a reminder to the folks who have been around since day one:
When adjusting graphics settings in-sim, restart the sim and the PC before testing the new settings out!
I recently replaced my 10700k with an 11900k on my Strix Z490-E board, and with hyperthreading disabled, it’s holding 5.3 ghz all-core, all day long with a Noctua NH-D15s.
I am incredibly impressed with the additional overhead and smoothness the CPU provides to the mainthread.
I, of course, have been playing with settings to see how much further I can take my traffic and LODs in relation to keeping my 3060ti happy while rendering on a Samsung G9. This included going into Nvidia Control Panel, dumping my previous settings in there and setting the slider to “performance” to reduce GPU render latency.
Back in the Sim, after adjusting LODs, leaving the menu, and continuing the flights to watch my render latencies, I noticed that my rdrthread and concurrentgtdraw latencies were spiking. Didn’t matter if I was on the ground at JFK, flying over NYC or STL, or parked on a ramp someplace. They were making a fuss and causing all kinds of stuttering, going so far as to interfere with the engine sounds.
I selected “reset to defaults” in the graphics and traffic menus and saved. I then set my graphics to default “Ultra”, set vsync to 30, saved again, closed out the sim, and restarted the PC.
Once back in the game, with the stock Ultra settings and vsync 30 that I set before shut down, everything was smoothed out, and no more spiking anywhere. It’s an old trick, but something I haven’t had to deal with for a long time.
For those curious, I was able to increase TLOD by 100, return Volumetric Clouds to Ultra, and run stock traffic settings, compared to the 5s on the sliders I had with the 10700k.
End result: Stock traffic settings, stock Ultra settings, in-game vsync set to 30, GPU limited and happy.
Side note: I believe the Volumetric Clouds were affected by some over-ambitious settings I had selected in NVCP. Returning the NVCP to “performance” on the slider opened up a ton of headroom on my GPU, which would have impacted the cloud rendering.
TL/DR: NVCP settings can negatively impact performance & restart your PC before testing in-game graphics settings