MSFS 2024 stutters: how do I fix freezes and lag?

To fix MSFS 2024 stutters, first identify whether the symptom is a brief micro-stutter, sustained low FPS, a camera-pan hitch or a mid-flight freeze. Test a stock aircraft with add-ons and traffic disabled, then target frame timing, scenery streaming, storage or the limiting CPU, GPU or VRAM resource.

• Micro-stutters are isolated pauses or dropped frames within otherwise smooth flight.
• Sustained low FPS means most frames are slow, usually because the main thread or GPU cannot maintain the requested workload.
• Camera-pan stutters appear when looking around, often through uneven frame pacing, newly visible scenery, VRAM pressure or a low base frame rate.
• Mid-flight freezes last longer or recur after time in the air, pointing towards streaming, memory growth, periodic utilities, heat or an add-on fault.

What MSFS 2024 micro-stutters look like

The location and trigger of an MSFS 2024 micro-stutter usually reveal more than the average FPS counter.

Use this repeatable stock-aircraft test flight

A controlled test flight separates a simulator-wide problem from an aircraft, airport or streaming problem.

1. Choose a simple baseline. Load the stock Cessna 172 or another default light aircraft at a default, non-handcrafted regional airport. Use clear weather and daylight.
2. Remove variable traffic. Turn off live and AI traffic, multiplayer, airport vehicles and external traffic injection for the test.
3. Use a fixed sequence. Sit on the runway for one minute, make a slow cockpit camera sweep, take off, fly one circuit, then continue straight for about ten minutes into new scenery.
4. Repeat the same views. Pan across the same buildings and terrain at the same points. Do not compare one airport departure with an unrelated flight.
5. Change one item. Adjust one setting group, cache option or add-on category, reload the test and repeat it. A change counts only if the same hitch improves consistently.

Frame-time spikes versus low average FPS in MSFS 2024

Micro-stutters are sharp frame-time spikes, while sustained low FPS is a continuous inability to produce frames quickly enough.

At 30 FPS, each frame has about 33.3 milliseconds; at 60 FPS, about 16.7 milliseconds. One frame taking 100 milliseconds causes a visible hitch even if the displayed average remains high. This is why an FPS average can look healthy while the camera still jerks.

On PC, use the MSFS 2024 Developer Mode FPS display and compare main-thread and GPU frame times. Total CPU utilisation is misleading because the simulator can saturate one critical thread while the other CPU cores remain partly idle.

A full-looking VRAM meter alone is not proof of exhaustion because some tools report allocated rather than actively used memory. Treat it as evidence when it coincides with repeatable camera hitches, texture loading or a sharp performance collapse.

Which settings should I change first?

Change settings that affect the measured bottleneck rather than reducing the entire preset.

If the display says the simulator is CPU-bound, follow our main-thread diagnosis and CPU-setting priorities. If the limit is unclear or FPS is continuously low, use our MSFS 2024 CPU, GPU, VRAM and streaming checks before sacrificing image quality.

Reducing every graphics setting to minimum is a mistake we see constantly. It can leave traffic or Terrain LOD saturating the main thread while making the simulator look substantially worse.

Why does MSFS 2024 stutter when looking around?

MSFS 2024 usually stutters when looking around because the new view exposes scenery and textures that were not visible, or because uneven frame delivery makes an otherwise stable pan appear jerky.

• Main-thread spike: Lower Terrain LOD, Object LOD and traffic when turning towards a city or terminal causes the CPU frame time to jump.
• GPU or VRAM spike: Lower render scale or texture resolution when every view change causes a GPU-time jump or high-resolution scenery exhausts the memory budget.
• Smooth frame times but jerky motion: Test one frame cap or V-Sync method and check that the monitor refresh rate and variable-refresh range suit the achieved FPS.
• Only with frame generation: Turn frame generation off and compare the same camera sweep. Generated frames cannot conceal a severe source-frame stall.

For head tracking, cockpit freelook and mouse-pan problems that remain after the clean test, use our camera-specific stutter test sequence.

Frame caps, V-Sync and frame generation

A sustainable frame cap often feels smoother than an uncapped rate that repeatedly rises and falls across a demanding target.

1. Establish the base rate. Turn frame generation off and test the same runway, cockpit and camera sweep. Note the lowest repeatable performance, not the maximum seen while looking at the sky.
2. Choose a sustainable target. Select a rate the system can hold in the demanding part of the test. A cap does not repair a 200-millisecond scenery stall, but it can provide steadier pacing and leave processing headroom.
3. Use one presentation limiter. Test the simulator’s V-Sync or frame limit, a driver-level cap, or a display-related limiter individually. Do not stack several caps while diagnosing the problem.
4. Check variable refresh. If the display supports it, keep the achieved rate within its useful refresh range. Repeatedly dropping below that range can feel like stutter even without a large FPS-counter change.
5. Test frame generation last. Enable it only after the source frame rate is reasonably stable, then repeat exactly the same camera movement and flight segment.

Frame generation can improve perceived motion when the base rate and frame times are stable. It can worsen uneven pacing, latency and visual artefacts when the GPU is saturated, VRAM is tight or the main thread is producing irregular source frames. Some limiters also count generated and rendered frames differently, so judge the observed motion and frame-time graph rather than assuming the configured number means the same thing everywhere.

How should I test rolling cache, photogrammetry and streamed scenery?

Compare the same route online and offline before clearing anything; this establishes whether streamed scenery or the rolling cache is involved.

1. Test the connection itself. Use the PC or console network test to check throughput, latency and packet loss. Pause operating-system downloads, cloud synchronisation and streaming video, and use Ethernet where practical. A high advertised speed does not compensate for packet loss or unstable latency.
2. Compare online and offline scenery. Search the simulator settings for Online Functionality and Photogrammetry. Fly the stock test with them enabled, then reload it with online scenery disabled. Reduced scenery detail offline is expected; the useful result is whether the pauses disappear.
3. Test rolling cache without deleting it first. Disable Rolling Cache through its in-simulator control and repeat the route. If that consistently fixes location-based stalls, delete the existing cache using the same control and create a new one on an SSD.
4. Judge a rebuilt cache fairly. An empty or newly recreated cache must download and store scenery again, so the first flight can stutter more. Fly the route at least twice before deciding whether rebuilding helped.
5. Check storage. Keep the simulator packages and rolling cache on an SSD where possible. Leave enough free space for streamed data, temporary files and the operating-system page file; a nearly full drive can produce stalls and failed cache writes.

Do not rebuild a healthy rolling cache after every update or every isolated pause. Rebuilding is justified when disabling it fixes a repeatable problem, cached scenery appears corrupt, or its storage location is failing or short of space.

If offline scenery is smooth but online scenery stutters across several stock locations, and the local connection test is clean, streamed-data delivery may be the limiting factor. Reinstalling the whole simulator will not correct a service-side or route-to-server problem.

How do I rule out the Community folder, FSTL and RCTP scenery?

An add-on remains a suspect until the same flight is smooth with all Community content and external utilities removed from the test.

1. Close MSFS 2024 fully. Locate the active Community folder; its path varies by store and custom installation. Move its contents to a temporary folder outside the simulator’s package directories rather than deleting them.
2. Stop external utilities. Close traffic injectors such as FSTL, moving maps, flight trackers, telemetry exporters, weather tools, recorders and overlays. A utility can affect frame timing even when it has no visible window.
3. Use default scenery. If the problem occurs at RCTP, remove any custom RCTP airport and overlapping regional scenery, then test the default airport. This does not prove the package is faulty; it checks for package conflicts and combined load.
4. Run the stock baseline. Use the default aircraft, clear weather and no traffic at the same location. If the stutter remains unchanged, continue with frame-time, streaming and system checks.
5. Restore add-ons by halves. Return half the packages, test, and keep dividing the group that brings back the stutter. This is much faster than testing a large library one item at a time.
6. Confirm the result. Test the suspected package alone and then with its required libraries. Some faults come from two individually working add-ons covering the same airport or supplying duplicate traffic models.

Disabling only the visible FSTL window may not remove its model packages, and emptying only the Community folder may leave an external injector running. Both sides of an add-on installation must be excluded.

I’m on Xbox: what should I do?

Xbox Series X|S users should replace PC-only Community-folder and driver steps with a complete simulator restart and optional-content test.

1. Quit the simulator fully. Use the console menu’s Quit command instead of leaving MSFS 2024 suspended or relying on Quick Resume.
2. Restart the console. Perform a normal console restart, then launch the simulator without opening unrelated applications first.
3. Remove optional content. Temporarily uninstall suspect aircraft, liveries and airport packages through the simulator’s installed-content controls. Test a stock aircraft and default airport.
4. Disable traffic and multiplayer. Repeat the flight without live traffic, AI traffic or multiplayer aircraft.
5. Compare online and offline scenery. Fly the same short route with online functionality and photogrammetry enabled, then disabled. A large improvement offline points towards streaming rather than a graphics-driver issue.

Do not delete Xbox saved data or reserved storage as an early troubleshooting step. It can force a large redownload or resynchronisation without addressing the cause. On PlayStation 5 and PS5 Pro, use the equivalent close, restart, optional-content and online-versus-offline tests; PC driver and Community-folder instructions do not apply.

Why does MSFS 2024 keep freezing mid flight?

A freeze that appears only after time in the air is more likely to involve cumulative memory use, streamed scenery, heat or a periodic add-on task than the departure airport alone.

1. Record the trigger. Note the elapsed flight time, location, camera action and whether audio, controls and the operating system continue responding.
2. Load near the freeze location. Start a fresh flight close to where it happened. An immediate repeat points towards that scenery area; a freeze only after the full route points towards time-dependent behaviour.
3. Remove periodic utilities. Disable traffic injection, trackers, telemetry, autosave tools, overlays and recorders. A freeze at a regular interval strongly implicates a scheduled task.
4. Compare aircraft. Repeat with a stock aircraft. Complex avionics or an aircraft-specific fault can accumulate work or memory during a long sector.
5. Watch resources on PC. Check whether RAM, VRAM, disk activity or temperatures steadily rise. Growth that occurs only with one add-on is useful evidence, although a high reading by itself does not prove a memory leak.
6. Distinguish a simulator stall from a system lock. A whole-computer freeze, repeating audio, graphics-driver reset or restart points towards temperatures, unstable overclocks, memory, storage or driver stability rather than an ordinary scenery setting.

Return CPU, GPU and RAM overclocks or undervolts to standard settings while testing. Keep the operating-system page file enabled and allow temporary shader compilation after a graphics-driver or shader-cache change.

Is MSFS 2024 stuttering fixed yet?

There is no single MSFS 2024 stutter bug with one yes-or-no status; simulator defects, shader compilation, streamed scenery, add-ons and hardware limits produce similar-looking pauses for different reasons.

For Sim Update 5, released in April 2026, the useful test remains the same: compare a repeatable stock flight with traffic, optional content and external utilities disabled. If that baseline is smooth, the simulator can run correctly on the system and the next task is to restore each workload category until the pause returns.

Still not working: what should I reset or reinstall?

If a stock, offline flight still stutters after the bottleneck and storage checks, repair settings and files before attempting a full reinstall.

1. Return experimental settings to a known baseline. Use a standard graphics preset, restart the simulator and retest. If settings or menus behave incorrectly, follow our safe MSFS 2024 graphics reset procedure.
2. Verify or repair simulator files. Use the installation platform’s repair or verification function. Preserve control profiles and record custom settings before any reset.
3. Review driver timing. If the problem began immediately after a graphics-driver change, use a stable driver that previously worked or a later stable release. Expect temporary shader-compilation hitches after changing drivers.
4. Check system stability. Investigate temperatures, memory errors, storage health and operating-system error records if the entire PC freezes or restarts.
5. Reinstall last. Reinstallation is justified after file repair fails and the clean baseline remains broken. It rarely fixes an add-on conflict, unstable connection, insufficient VRAM or an unsustainable graphics workload.