I’ve found that, apart from the other strange effects it causes at the moment, supersampling causes a big hit in FPS, without (for me) any noticeable increase in quality. So keep that rendering down to 100% max.
Personally I’m fully maxed. I read over on Avsim that oddly enough having the pre-cache of terrain data set to ultra gives you better performance than on low. I personally haven’t tested this but given I’m fully maxed out I’m curious what happens if I drop this and only this to low. I will try this out in a bit and report my findings.
This video came out a week or two after MSFS launched. It shows a side by side of just about all of the graphics settings. It’s long, so grab paper and pencil, plus a snack. The things that make a big difference can be set to high/ultra, while the things that make very little visual impact (and sometimes the biggest frame impact) can be set lower. I’ll paste in my settings list below, with my core specs at the bottom. I just did a test with the drone over Manhattan, and with these settings, I was getting 30+ FPS. It does drop when loading new scenery, and with the drone’s speed maxed out, I was still getting ~25 FPS at max transit speed. If I stop and let everything load, I’m back in the 30’s.
V-Sync > Off
Anti-Aliasing > TAA
Terrain LOD > 100
Off Screen Terrain Pre-caching > High
Terrain Vector Data > Medium
Buildings > Medium
Trees > High
Grass/Bushes > High
Objects LOD > 50
Clouds > Ultra
Texture Resolution > Low
Anisotropic Filtering > 4x
Texuture Supersampling > 4x4
Texture Synthesis > Low
Water Waves > High
Shadow Maps 2048
Terrain Shadowns 128
Contact Shadowns > Ultra
Windshield Effects > High (no glass screen reflections)
Ambient Occlusion > Ultra
Reflections > Ultra
Bloom > On
Depth of Field > Off
Lens Correction > Off
Lens Flare > Off
Glass Refresh Rate > High
OP: We have similar graphics cards (I have a 2070 non-super), and I have a slightly better CPU (Ryzen 5600X), and I can can run everything on Ultra at 2560X1440.
I would suggest starting on the ultra preset and tweak down from there (if needed). However, I have a fixed FPS of 30 and I’m not worried about maximizing FPS. 30 FPS is smooth and easy to obtain on Ultra.
I agree that this will result in higher FPS … but I can only fly with V-sync = ON because otherwise each frame has some disturbing vertical discontinuity, at some changing random place, which my brain gets so attracted to that it totally kills the immersion for me.
I have a few standard “benchmark runs” I do with CapFrameX. I use the exact same settings (including date and time); no traffic or MP for repeatability, etc. Fly the same way and engage autopilot ASAP to avoid accidental changes.
So I simply ran these with the low setting and with the ultra setting. From two of the runs I got this:
So at almost every point of the run, I had about 7-10 fps higher with the low setting.
However, there’s no camera motion in this benchmark, and if there had been, there would have been far more stuttering with the low setting. I find it almost unplayable.
I think for the most part they are. The core code has been changed to increase overall performance, but individual settings can still have an effect on performance. So I keep the settings that have next to no visual impact dialed back to save resources. Prior to the major code update that gave most people these current frames, Manhattan and London would bring my rig to its knees. Now I get fluid frames most of the time. There are still times that I get a momentary stutter down to about 5 FPS, but those don’t last long, and it’s usually when the sim is having to load scenery at low altitude, and usually on approach. I’m hoping the increased caching ability will help that.
Same for me. What I learned a few months ago was that since i have a fixed refresh rate monitor, I should target 30 or FPS and turn on vertical refresh.
It turned out that my experience in the game was much better at 30 FPS than f.ex. 50 FPS using these settings.