How do I fix MSFS 2020 stuttering and micro-pauses?
To fix Microsoft Flight Simulator 2020 stuttering on PC, test an empty Community folder, disable or rebuild the rolling cache, and cap FPS at a sustainable level. Use the built-in FPS display to identify a main-thread, GPU or streaming bottleneck; on Xbox, fully restart the sim and isolate optional content.
Why does MSFS 2020 stutter even when FPS looks good?
Good average FPS does not guarantee smooth motion because stuttering is caused by inconsistent frame times. A flight fluctuating between 35 and 60 FPS can feel rougher than one holding a steady 30 FPS.
Microsoft Flight Simulator 2020 has several workloads that arrive in bursts: terrain and airport objects, photogrammetry, traffic, cockpit displays, weather, add-on scripts and texture uploads. Frame generation can raise the displayed FPS, but it cannot hide a serious main-thread stall or data-loading pause.
| Symptom | Likely cause | First test |
|---|---|---|
| Stutter near cities or large airports | Main-thread pressure from LOD, traffic, scenery and cockpit displays | Lower Terrain LOD, Object LOD and traffic |
| Hitch when looking around or changing views | Off-screen scenery loading, VRAM pressure or slow storage | Check Offscreen Terrain Pre-Caching and reduce memory-heavy settings |
| Pause at a regular interval | Cache activity, an injector, overlay, monitoring utility or background task | Disable the rolling cache and close external utilities |
| Only one aircraft or airport stutters | Aircraft systems, avionics, scenery or another add-on conflict | Repeat the flight with default content |
| Offline flying is smooth | Scenery streaming, live traffic, multiplayer or connection variability | Re-enable online features individually |
Fix MSFS 2020 stuttering in the right order
The fastest way to find the cause is to change one variable at a time on a repeatable test flight. Randomly reducing every graphics setting can conceal the problem without showing which change helped.
- Fully restart the simulator. Do not resume a suspended session for testing. After a simulator or graphics-driver update, fly the same short route twice before judging it because shaders and scenery assets may be cached during the first run.
- Create a controlled baseline. Use the same simple default aircraft, airport, weather preset, time of day and camera movement. Start somewhere moderately demanding rather than at the largest handcrafted hub available.
- Identify the limiting component. On PC, enable the simulator’s Developer Mode FPS display. If it reports
Limited by MainThread, concentrate on LOD, traffic and cockpit refresh. If it reportsLimited by GPU, reduce render scaling and graphics effects instead. - Test without add-ons. Close any add-on manager, move the contents of
Communityto a temporary location outside the simulator’s package folders, and repeat the test. Do not delete or move theOfficialfolder. - Disable other third-party content. An empty
Communityfolder does not disable Marketplace packages or external SimConnect utilities. Temporarily disable suspect aircraft and scenery through Content Manager, and close traffic injectors, flight recorders and other connected utilities. - Test online services together, then separately. Turn off photogrammetry, Bing world data, multiplayer, live traffic and live weather for one flight. If that removes the stutter, restore each service individually until the hitch returns.
- Clear or disable the rolling cache. Use the rolling-cache controls in the simulator’s Data settings rather than deleting unrelated package files. If rebuilding the cache restores smoothness, keep it on a fast SSD; if the pauses return, leave it disabled and compare again.
- Apply a sustainable FPS cap. Choose a target the computer can maintain at the demanding part of the flight, not merely in cruise. Use only one limiter while testing so that the simulator, graphics driver and another utility are not fighting one another.
- Change settings that match the bottleneck. Lower CPU-heavy settings for a main-thread limit and GPU-heavy settings for a graphics limit. Re-test after every meaningful change.
- Check the wider system. Close browsers, recording overlays, cloud synchronisation, RGB utilities and excessive hardware monitoring. Keep security software enabled, but avoid running a scheduled scan during the test.
Which MSFS 2020 settings should I lower first?
Lower the settings responsible for the active bottleneck rather than starting with a global quality preset. Terrain LOD will not solve a graphics card saturated by resolution, while reducing cloud quality does little for a main thread overwhelmed by airport traffic.
| Bottleneck | Signs | Settings to change first |
|---|---|---|
| Main thread | Worst at airports, cities or in complex cockpits; FPS display names MainThread | Terrain LOD, Object LOD, live or AI traffic, ground aircraft, airport vehicles and glass-cockpit refresh rate |
| GPU | Graphics limit shown; performance worsens with resolution, clouds or external views | Render scaling, cloud quality, shadows, reflections and ambient occlusion |
| VRAM or scenery loading | Hitches when panning, switching views or entering a detailed area | Texture resolution and render scaling; review Offscreen Terrain Pre-Caching |
| Streaming | Offline mode is smooth, often with delayed or blurry scenery online | Photogrammetry, Bing world data, rolling cache and manual cache where available |
Offscreen Terrain Pre-Caching needs special treatment. Raising it can reduce camera-panning stutters because scenery outside the present view remains prepared, but it consumes more memory. Raise it when view changes hitch and memory capacity is available; lower texture and resolution demands instead if the system is already running out of memory or VRAM.
DLSS or another upscaler can help when the GPU is the limit, but it will not repair a MainThread bottleneck. Disable frame generation while diagnosing the base performance because generated frames can make the FPS counter look healthy while genuine simulation stalls remain.
How should I cap the frame rate?
Set the cap to the rate MSFS can hold during approach at a representative airport. A steady 30 or 40 FPS usually gives cleaner motion than repeated swings between much higher and lower values, provided the display’s refresh behaviour supports that target.
With a fixed-refresh display and V-Sync, a target that divides evenly into the refresh rate often produces better pacing. Variable-refresh displays tolerate a wider range, but they cannot correct a long CPU, storage or streaming stall.
Why does MSFS 2020 stutter near airports or on approach?
Approach combines many of the simulator’s heaviest tasks at once: detailed scenery, terrain loading, traffic logic, airport vehicles, cockpit displays, lighting and weather. A system that is smooth in cruise can therefore become main-thread limited on final.
- Lower Terrain LOD and Object LOD if the FPS display identifies the main thread.
- Reduce live traffic, ground aircraft and airport vehicles at busy hubs.
- Lower glass-cockpit refresh rate when a complex airliner is much rougher than a simple default aircraft.
- Test photogrammetry off if the problem is concentrated around a detailed city.
- Disable the airport add-on if only one location is affected.
Do not tune the entire simulator around one unusually demanding airport. Compare that location with default scenery and a default aircraft first; if only the add-on combination stutters, update, reconfigure or remove the package responsible.
What causes micro-pauses every few seconds?
A pause occurring at a regular interval usually comes from a repeating process rather than insufficient average performance. Rolling-cache writes, traffic injection, autosave utilities, overlays, cloud synchronisation and hardware polling are common sources.
- Disable the rolling cache and repeat the same flight.
- Turn off online data and live services to rule out repeated network or scenery-streaming delays.
- Close external simulator utilities, especially traffic, recording, telemetry and autosave tools.
- Stop non-essential overlays and monitoring rather than leaving several applications polling the simulator and hardware.
- Disconnect unnecessary USB devices if Windows is repeatedly losing and rediscovering a controller or peripheral.
- Try another aircraft if the timing begins only after avionics or cockpit systems finish loading.
If the hitch follows camera movement rather than a fixed interval, investigate off-screen terrain caching, VRAM and storage instead. If it follows one geographic location, suspect scenery or streamed data for that area.
Should I use DX11 or DX12 for smoother frame times?
Neither graphics API is universally smoother, although DX11 is the conservative troubleshooting baseline for MSFS 2020. DX12 performs well on some systems but changes memory behaviour and can expose VRAM pressure that was less visible under DX11.
Compare both APIs with the same aircraft, route, weather and settings, restarting the simulator after each change. Repeat the test once before recording the result because the first run after switching APIs or changing a display driver can include shader-related hitches. Do not clear shader caches repeatedly; that can force the simulator to rebuild work you are trying to measure.
If stuttering began immediately after a graphics-driver change, install a stable replacement or return to the last version that worked correctly on that PC. Avoid combining a driver change, API switch and graphics-preset reset in one test.
Do SSD placement, cache and World Updates matter?
Yes, although storage changes help loading pauses more than a true CPU or GPU bottleneck. Keep the simulator’s package content, Official and Community folders, and any rolling or manual cache on SSD storage with sensible free space.
Leaving the launcher or base installation on one drive and package content on another is not inherently a problem when both drives are fast and healthy. If two simulator generations are competing for space, our guide to splitting MSFS 2020 and 2024 across separate drives explains which package locations matter.
Leave the Windows page file system-managed on SSD storage. Disabling it does not create free performance; under memory pressure it can turn an ordinary slowdown into severe pauses or a crash.
World Updates consume storage and add detailed regional scenery, but removing all of them is not a universal performance fix. Remove an update to reclaim space or to test a problem confined to its region; our explanation of when optional World Updates deserve the disk space helps with that decision.
How do I troubleshoot MSFS 2020 stuttering on Xbox?
On Xbox, skip the PC-only Community, Developer Mode FPS and DX11/DX12 steps. Fully quit Microsoft Flight Simulator rather than resuming its suspended state, restart the console, and repeat a short flight with the rolling cache and online services disabled.
Use Content Manager to disable suspect Marketplace aircraft, airports and regional scenery. If a default aircraft at a default airport is smooth, restore optional content in small groups until the problem returns.
Do I need to reinstall Microsoft Flight Simulator?
No—reinstallation should be the last step because it does not fix an overloaded main thread, unstable scenery streaming or an incompatible add-on. Use the platform’s file verification or repair option first, then retest with third-party content disabled and a fresh rolling cache.
Reinstall only when files repeatedly fail verification, the simulator cannot load clean default content, or corruption remains after the controlled tests above. Depending on the chosen package location, reinstalling the base application may leave add-ons and cached data untouched, so it is not automatically a clean test.