How do I improve MSFS 2024 FPS and performance?
To improve FPS in Microsoft Flight Simulator 2024, first determine whether the main thread, GPU, VRAM or scenery streaming is limiting the flight. Lower only the settings tied to that bottleneck—usually render scaling, terrain and object detail, traffic or clouds—then retest the same scenario. Stable frame time matters more than peak FPS.
Microsoft Flight Simulator 2024, also shortened to MSFS 2024 or FS2024, can show a high average frame rate while still juddering on final approach. Aim for a frame rate the PC can sustain at a detailed airport in poor weather, not a brief maximum over empty countryside.
How do I establish a reliable performance baseline?
A repeatable test flight lets you see whether a change genuinely improves MSFS 2024 performance.
- Update the simulator and graphics driver. If performance deteriorated immediately after a driver update, the previous known-good driver may be a better test than repeatedly changing simulator settings.
- Eliminate power and storage problems. Use an SSD, connect a laptop to mains power, select the dedicated GPU and check that CPU or GPU temperatures are not causing thermal throttling.
- Start with default content. Temporarily remove Community-folder add-ons and use a default aircraft, default airport and simple weather preset. Installed Marketplace or official packages are separate from the Community folder, so disable recently added content there as well if necessary.
- Repeat one demanding scenario. Use the same gate, aircraft, time, weather and camera position. Comparing a clear rural flight with an overcast arrival at a major hub tells you nothing useful.
- Read the performance display. The simulator's built-in FPS display can report a main-thread or GPU limit. Watch frame time and the limiting component, not just the FPS counter.
Close browser tabs, recording software, hardware-monitor overlays and unnecessary RGB or peripheral utilities during the baseline. A mistake we see constantly is altering ten settings at once while several add-ons and overlays remain active.
Which settings give the biggest MSFS 2024 FPS boost?
The most effective setting depends on the bottleneck; turning every option to Low wastes visual quality and may leave the real limit untouched.
| Setting group | Lower it when | Main trade-off |
|---|---|---|
| Render scaling or upscaling quality | The GPU is limiting performance, especially at high display resolutions | Softer instruments, runway markings and distant detail |
| Terrain Level of Detail | The main thread struggles over cities or on approach | Shorter terrain draw distance and more visible loading |
| Objects Level of Detail | Dense buildings, airports and scenery cause CPU-limited frame times | Objects appear at shorter distances |
| Traffic and airport activity | FPS is worst at the gate but improves after departure | Less live or AI traffic and quieter airports |
| Cloud quality | Overcast and storms perform much worse than clear weather | Less detailed cloud formations |
| Shadows, reflections and ambient effects | You need GPU headroom without reducing world detail | Less shadow definition, depth and reflection quality |
| Texture quality | VRAM is full and camera movement causes swapping or severe hitches | Less detailed surfaces; often little FPS gain when VRAM is sufficient |
| Photogrammetry and online scenery | Pauses coincide with new scenery downloading or an inconsistent connection | Less detailed streamed cities; this may not improve FPS on a healthy connection |
For a GPU limit, reduce render scaling in small steps before dismantling the rest of the graphics preset. For a main-thread limit, start with traffic, Terrain Level of Detail and Objects Level of Detail. Our detailed PC and VR graphics recommendations cover the finer balance between image quality, resolution, LOD and traffic.
Should I use frame generation?
Frame generation can make motion look smoother on supported hardware, but it does not repair an unstable base frame rate. It inserts generated frames between rendered ones, so the FPS counter rises without proportionally improving simulation response or main-thread frame time.
Enable it only after the underlying flight is reasonably smooth. If taxiing already produces long stalls, frame generation may hide some unevenness but can introduce latency, display artefacts around instruments or ghosting during rapid camera movement.
Am I CPU-limited or GPU-limited?
Resolution-sensitive performance usually indicates a GPU limit, while airport-, traffic- and aircraft-sensitive performance usually points to the CPU's main thread.
Signs of a GPU limit
- Lowering render scaling produces an immediate improvement.
- Clouds, shadows, reflections and anti-aliasing have the largest effect.
- FPS falls substantially when display resolution rises.
- The performance display reports a GPU limit and graphics-card usage remains high.
Signs of a main-thread limit
- Large airports, detailed cities, traffic and glass-cockpit aircraft cause the largest losses.
- Reducing resolution or render scaling barely changes FPS.
- Traffic and terrain or object detail help more than texture and cloud settings.
- The simulator reports a main-thread limit even though total CPU utilisation looks modest. One busy core can be the limit while the overall percentage remains low.
Signs of VRAM or scenery-streaming pressure
- Turning the camera causes sudden hitches, delayed textures or large usage swings.
- The problem worsens with high texture settings, high resolution or detailed scenery packages.
- Pauses occur mainly when entering a new area and improve when photogrammetry is disabled.
- Performance becomes poor only where two scenery packages cover the same airport or city.
VRAM pressure is not the same as a generally slow GPU. Lowering textures can reduce swapping and stutters when memory is full, but it is usually a poor first choice when the card has spare VRAM.
How do I fix stutters in MSFS 2024?
Fix stutters by matching the change to where and when each frame-time spike occurs.
- At the gate or during taxi: reduce live or AI traffic, multiplayer aircraft, parked aircraft, airport vehicles and worker density.
- On final approach or over a city: lower Terrain Level of Detail and Objects Level of Detail, then test photogrammetry off for one identical flight.
- In overcast or storms: reduce cloud quality. A clear-weather preset is a useful diagnostic test, but it is not a permanent fix if you want live weather.
- When entering a new scenery area: check the connection and rolling cache. Keep the rolling cache on an SSD and rebuild it only when corruption is suspected; clearing it routinely forces the simulator to download the data again.
- At regular intervals: close overlays, capture tools and browsers, then test without traffic utilities or other continuously running add-ons.
- With high FPS but choppy motion: use V-sync, variable refresh or a frame cap appropriate to the display. Choose a limit the system can maintain in demanding conditions rather than one it reaches only in cruise.
- After a driver or simulator update: allow for one-off shader and scenery-cache rebuilding. Repeatedly deleting caches can recreate the very stutter being diagnosed.
Why does performance collapse at large airports?
Major airports combine the simulator's heaviest CPU, graphics and streaming loads in one location.
Detailed terminals, service vehicles, parked aircraft, live traffic, complex avionics and nearby city scenery all compete for frame time. Reduce airport activity and LOD before lowering texture quality, particularly when performance improves markedly after take-off.
Test the same stand with a default aircraft and then a default airport. If only one third-party airport is affected, check for duplicate scenery, overlapping airport packages or an active default package that the add-on was designed to replace.
Can add-ons reduce FPS or cause crashes?
Aircraft, airports, traffic tools and overlapping scenery can cause low FPS, freezes or crashes even when the graphics settings are sensible.
- Remove Community content temporarily. Renaming or moving the active Community folder is often faster than deleting individual packages.
- Disable other recently installed content. An empty Community folder does not disable packages installed through the simulator's content system.
- Retest with a default aircraft and airport. Keep the weather, stand and camera unchanged.
- Restore packages in small groups. When the problem returns, divide that group until the responsible add-on or conflict is identified.
If poor performance has progressed to freezes or crash-to-desktop events, use our separate MSFS 2024 crash-troubleshooting checklist rather than treating every crash as an FPS problem.
MSFS 2024 live weather not working: what should I check?
If MSFS 2024 live weather is not working, verify the selected weather mode and online-data controls before changing graphics settings.
- Select Live Weather for the flight. Make sure a manual preset has not carried over from an earlier performance test. Use a normal free-flight session to isolate the feature because some activities can prescribe conditions.
- Enable online functionality. Disabling online services to reduce scenery streaming can also stop live weather, live traffic and other connected features.
- Restart the flight and simulator. A failed online session or weather injection can affect one launch without indicating a permanent configuration fault.
- Test without weather or toolbar add-ons. Use default content before assuming the graphics driver or cloud-quality setting is responsible.
- Check the other live services. If photogrammetry, live traffic and live weather all fail together, investigate the connection, account session, data limit or a service-side interruption.
- Judge the result broadly. Wind, pressure and cloud coverage should be plausible, but a short delay or a visual difference from an airport report does not by itself prove that weather injection has failed.
Our guide to MSFS 2024 data use and bandwidth controls explains which online features consume data and what can be disabled without guesswork.
If live weather loads but heavy cloud layers reduce FPS, lower cloud quality. The live-weather connection itself is not normally the expensive graphics workload; rendering the resulting cloud scene is.
Why did MSFS 2024 performance change after an update?
Simulator updates can alter rendering, memory use, traffic behaviour and the balance between the main thread and GPU.
Recheck output resolution, render scaling, traffic and assistance settings after a major patch because saved options may no longer behave exactly as before. Add-ons may also need updates, while rebuilt shaders can make the first run less representative than later tests. The performance changes introduced with Sim Update 3 illustrate why old benchmark results should not be treated as permanent.
What if lowering sensible settings barely helps?
If several relevant settings make almost no difference, the simulator is probably capped, limited by another component or affected by a system-level problem.
- Check for an active V-sync or frame-rate cap if FPS remains fixed at an exact value.
- If lower render scaling changes nothing, investigate a main-thread, traffic or external frame-cap limit.
- If lower traffic and LOD change nothing, investigate GPU load, cloud quality, resolution and VRAM use.
- Confirm that the simulator is using the dedicated GPU and that the PC is not throttling because of temperature or laptop power mode.
- Keep the simulator, packages and rolling cache on SSD storage with adequate free space.
- Leave the Windows page file system-managed. Disabling it, forcing process priority or applying unverified configuration edits can create instability without removing the real bottleneck.
When the target frame rate remains unattainable in the worst-case airport and weather after clean testing, lower the target or upgrade the component identified by the performance display. No configuration tweak can turn a sustained hardware limit into spare frame time.