Fix Microsoft Flight Simulator stuttering at high FPS by identifying frame-time, MainThread, VRAM, streaming, add-on and V-Sync problems.
Microsoft Flight Simulator can stutter at a good FPS because the counter shows throughput, not evenly timed frames. Brief MainThread stalls, scenery streaming, VRAM eviction, add-ons or mismatched V-Sync/VRR pacing create visible hitches without ruining the average. Diagnose the frame-time spikes first, then fix the limiting subsystem.
Why does MSFS stutter when the FPS counter is high?
A good average FPS does not guarantee smooth frame delivery. At 60 FPS, each frame should take about 16.7 milliseconds; one frame taking 70 milliseconds produces a visible hitch even if the counter continues to report close to 60.
Frame Generation can make this more confusing because a counter may include generated frames. It cannot hide a CPU, storage or scenery-streaming pause, so the displayed rate can look excellent while the base simulation remains uneven. Our explanation of why high FPS can still look choppy covers the distinction between frame rate and frame pacing in more depth.
| What the stutter looks like | Likely cause | First check |
|---|---|---|
| Regular judder during camera pans | Refresh-rate, frame-cap or V-Sync mismatch | Test a stable cap and VRR |
| Hitch when approaching new scenery | Photogrammetry, storage or rolling-cache activity | Compare with photogrammetry disabled |
| Stutter at detailed airports | MainThread load, traffic, airport scenery or VRAM pressure | Reduce traffic and LOD, then disable the airport add-on |
| Pause at a fixed interval | Add-on, SimConnect client, autosave, overlay or hardware utility | Close external utilities and test a clean configuration |
| High generated FPS but poor responsiveness | Low or unstable base frame rate | Disable Frame Generation while diagnosing |
How do I find what is causing the stutter?
The fastest diagnosis is to reproduce one hitch and watch which frame time spikes. On PC, Microsoft Flight Simulator's Developer Mode FPS display identifies whether the simulation is limited by the MainThread or GPU.
- Create a repeatable test. Use the same aircraft, airport, weather, camera and runway position after each change. A busy handcrafted airport is useful for a worst-case test, but also compare it with a default aircraft at a quiet default airfield.
- Disable Frame Generation temporarily. This exposes the real rendering rate and prevents generated frames from disguising an unstable base rate.
- Watch the hitch itself. If MainThread time jumps, concentrate on terrain and object LOD, traffic, complex aircraft and add-ons. If GPU time jumps, reduce rendering or VRAM-heavy settings. A spike without either limit often points to streaming, storage or an external program.
- Run a clean-content comparison. Temporarily remove or rename the PC
Communityfolder and disable marketplace or library add-ons. Test a default aircraft and airport, then restore content in small groups until the stutter returns. - Separate online scenery from local rendering. Compare the same flight with photogrammetry, live traffic and other online data disabled. Microsoft Flight Simulator 2024 streams more content than MSFS 2020, making this comparison particularly useful.
On Xbox and PlayStation 5, use the same controlled comparisons without Developer Mode: default content, reduced traffic, online scenery off and add-ons disabled one category at a time. For broader setting-by-setting diagnosis, use our MSFS bottleneck and performance checklist.
Which settings fix high-FPS stuttering?
Change the setting group tied to the bottleneck rather than lowering everything indiscriminately.
| Bottleneck | Settings or features to test | Common mistake |
|---|---|---|
| MainThread | Terrain LOD, Object LOD, live or AI traffic, ground aircraft and airport vehicles | Lowering resolution, which mainly helps the GPU |
| GPU | Render scaling, clouds, shadows, reflections and anti-aliasing mode | Reducing traffic while leaving GPU-heavy settings unchanged |
| VRAM | Texture resolution, render scaling, detailed airport scenery and high LOD values | Assuming spare system RAM prevents graphics-memory eviction |
| Streaming | Photogrammetry, rolling cache, network stability and package/cache storage | Treating a fast speed test as proof that streamed data cannot stall |
| Add-ons | Aircraft, scenery, traffic injectors, avionics, weather tools and SimConnect clients | Testing only the Community folder while leaving installed library content active |
Keep Microsoft Flight Simulator and its package or cache data on a healthy SSD where possible. Close recording overlays, browser video, RGB or peripheral utilities and flight-tracking tools during the test. If the pause happens at an exact interval, these background programs deserve attention before graphics settings do.
A graphics-driver update can also trigger temporary shader-compilation hitches as locations and effects are encountered again. Occasional first-run pauses may settle, but repeated stuttering on every flight indicates another cause.
Should I cap Microsoft Flight Simulator FPS?
Yes, when the uncapped rate fluctuates enough to produce uneven frame times. Choose a cap the busiest part of the flight can sustain, not the highest rate seen in cruise: 60 FPS is useful only if it remains close to 60, while a stable 30 or 40 can look smoother than constant swings between 40 and 70.
Fixed-refresh displays favour rates that divide evenly into the refresh rate. VRR displays allow more flexibility, although the rate should remain inside the display's working range. Apply one limiter while testing rather than stacking simulator, driver and third-party caps; our guide to choosing a sustainable simulator FPS cap explains the decision.
Should I use V-Sync or VRR to remove stutter?
Use VRR when the display supports it, because it can match refreshes to variable frame delivery within its operating range. V-Sync can provide clean pacing when MSFS holds the refresh rate or an exact divisor, but it cannot repair MainThread, streaming or add-on pauses.
If camera pans judder consistently rather than pausing sporadically, test V-Sync, VRR and the cap before changing scenery settings. Avoid changing all three at once; the practical combinations are covered in our explanation of how V-Sync, VRR and frame caps interact in MSFS.
Should I clear the MSFS rolling cache?
Clear and recreate the rolling cache once if stuttering began after an update, the cache appears corrupted or the simulator repeatedly hitches while loading streamed terrain. Where the option is available, also compare with the cache disabled or placed on a fast drive.
Do not clear it after every flight. That forces scenery to be downloaded again and can make the next visit to an area less smooth. Reinstalling the entire simulator is likewise a last resort because it does not correct frame pacing, overloaded settings or a conflicting add-on.
Why is stuttering worse at detailed airports?
Detailed airports combine the heaviest MainThread, VRAM and add-on loads in one place. Large terminal models, parked aircraft, road and ground traffic, complex airliner systems and nearby photogrammetry can create frame-time spikes even when cruise performance is excellent.
Test the airport with a default aircraft, traffic reduced and the airport add-on disabled. If the hitch disappears only when Terrain LOD or traffic is lowered, it is primarily a MainThread limit; if lowering texture resolution or render scaling fixes it, VRAM or GPU load is the stronger suspect. This distinction prevents the mistake we see constantly: sacrificing image quality when traffic or scenery complexity is actually blocking the CPU.