Boost MSFS 2024 FPS by finding CPU, GPU, VRAM or streaming limits, then tuning the settings that matter and fixing stutters.
To improve MSFS 2024 FPS, identify whether Microsoft Flight Simulator 2024 is limited by the CPU main thread, GPU, VRAM or scenery streaming. Then lower only the settings tied to that bottleneck, retest the same demanding flight, and cap the result at a frame rate the system can sustain smoothly.
Stable frame time matters more than the highest number shown over empty countryside. Tune for a detailed airport, complex aircraft and poor weather—the conditions in which low FPS and stutters are most noticeable. This diagnostic method applies to the Sim Update 5 codebase and remains useful when later updates shift the performance balance.
How do I establish a reliable MSFS 2024 performance baseline?
A repeatable test is the only dependable way to tell whether an optimisation has worked.
- Update and restart. Install the intended simulator and graphics-driver updates, then restart the PC. If performance deteriorated immediately after a driver change, testing the previous known-good driver is more useful than changing dozens of simulator options.
- Use one demanding scenario. Keep the aircraft, stand, airport, weather, time, traffic and camera position identical. A gate at a large airport or a repeatable final approach exposes limits that a rural cruise will hide.
- Begin with stock content. Use a relatively simple default aircraft and an unmodified airport. Temporarily remove Community-folder packages and disable recently installed content managed elsewhere in the simulator.
- Disable frame generation for diagnosis. It can raise the displayed FPS without improving the underlying main-thread or GPU frame time. Temporarily remove V-Sync and external frame caps as well if they prevent the true limit from appearing.
- Read the performance overlay. On PC, the built-in developer display can identify a main-thread or GPU limit. Our instructions for opening and interpreting the built-in FPS counter explain the available methods.
- Change one setting group at a time. Retest before making another change, then validate the result during an arrival rather than trusting a short test at altitude.
Close browsers, capture tools, unnecessary overlays and peripheral utilities during the baseline. A mistake we see repeatedly is changing ten graphics settings while traffic injectors, recording software and several add-ons remain active.
Am I CPU-limited, GPU-limited or short of VRAM?
Resolution-sensitive performance usually indicates a GPU limit, while airport-, traffic- and aircraft-sensitive performance usually points to the CPU main thread.
| What you observe | Likely limit | Best first test |
|---|---|---|
| Lowering render scaling immediately improves FPS | GPU | Reduce output resolution, render scale, clouds, shadows or reflections |
| Large airports and traffic are slow, but lower resolution barely helps | CPU main thread | Reduce traffic, Terrain Level of Detail and Objects Level of Detail |
| Camera turns cause hitches, delayed textures or sudden memory swapping | VRAM pressure | Lower texture resolution, render resolution or memory-heavy scenery |
| Pauses occur mainly when entering new scenery areas | Streaming, cache or storage | Test photogrammetry off, check the connection and use SSD storage |
| FPS remains fixed at an exact value regardless of settings | Frame cap or V-Sync | Check simulator, driver and third-party frame-limit controls |
Low total CPU utilisation does not rule out a CPU bottleneck. Microsoft Flight Simulator can be limited by one heavily loaded thread while the operating system reports plenty of unused capacity across the remaining cores.
VRAM pressure is different from having a generally slow graphics card. Lowering textures can remove swapping and camera hitches when memory is full, but it often produces little extra FPS when sufficient VRAM remains available.
Which settings give the biggest MSFS 2024 FPS boost?
The largest FPS gain comes from lowering the setting that feeds the active bottleneck, not from selecting the lowest graphics preset.
| Setting | Lower it when | Visual cost |
|---|---|---|
| Render scaling or upscaling quality | The GPU is limiting performance, particularly at high resolution | Softer cockpit displays, runway markings and fine detail |
| Terrain Level of Detail | The main thread struggles around cities or during approach | Shorter terrain draw distance and more visible distant loading |
| Objects Level of Detail | Dense airports, buildings and scenery produce a CPU limit | Buildings and objects appear at shorter distances |
| Live, AI and multiplayer traffic | Performance is worst at the gate or near a busy hub | Fewer aircraft and less convincing airport activity |
| Airport vehicles, workers and parked aircraft | Taxi and gate performance are much worse than cruise | Quieter aprons |
| Cloud quality | Overcast and storm conditions are substantially slower than clear weather | Less detailed cloud formations |
| Shadows, reflections and ambient effects | The GPU needs headroom but world detail is acceptable | Less depth, shadow definition and reflective detail |
| Texture resolution | VRAM is full or texture swapping causes severe hitches | Less detailed surfaces; little benefit when memory is not constrained |
| Photogrammetry and streamed scenery | Stalls coincide with scenery downloads or an inconsistent connection | Less detailed streamed cities; no guaranteed FPS gain on a healthy connection |
For a GPU limit, reduce render scaling in small steps before dismantling the rest of the preset. For a main-thread limit, begin with traffic, Terrain Level of Detail and Objects Level of Detail. Settings such as anisotropic filtering usually offer poor performance returns compared with the loss of image quality.
Resolution, display size and VR change the sensible starting point. We maintain practical starting settings for PC monitors and VR headsets covering render scale, LOD, clouds, textures and hardware expectations.
Should I use frame generation or an upscaler?
Upscaling reduces the GPU rendering workload, while frame generation creates intermediate displayed frames; neither removes a CPU main-thread bottleneck.
Use an upscaler when the GPU is the limit and the resulting cockpit text remains clear enough. Quality-oriented modes suit moderate resolutions, while more aggressive modes trade increasing sharpness and instrument readability for performance.
Enable frame generation only after the underlying flight is reasonably stable. It can make camera movement look smoother, but it does not speed up the simulation, aircraft systems or input response. Long stalls remain long stalls, and generated frames may add latency or visual artefacts around fast-moving edges. Tune with it off, then enable it for the final comparison.
How do I fix stutters and frame drops in MSFS 2024?
Stutters are best diagnosed by where and when the 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: lower Terrain and Objects Level of Detail, then compare a stock airport and aircraft. Our airport and approach-specific troubleshooting steps cover the workload that appears as the destination loads.
- Over dense cities: test photogrammetry off for one identical flight. If the pauses disappear, investigate the connection, rolling cache and streamed scenery rather than lowering every graphics option.
- In overcast weather: reduce cloud quality. Clear weather is a diagnostic comparison, not a permanent solution for anyone who normally flies with live weather.
- When turning the camera: watch VRAM use and test lower texture or render resolution. Detailed aircraft and overlapping scenery packages can consume memory even when average FPS appears acceptable.
- At regular intervals: disable traffic utilities, toolbar tools, recording software and other continuously running add-ons. Regular spikes often come from a background process rather than the rendering preset.
- With high FPS but choppy motion: use variable refresh, V-Sync or a sustainable frame cap. Avoid contradictory caps in the simulator, graphics driver and third-party tools.
Keep the rolling cache on an SSD if it is enabled. Rebuild it when corruption is genuinely suspected, not as routine maintenance: deleting a healthy cache forces scenery to download again and can recreate the stutter being investigated. Cache rebuilding after a simulator or driver update can also make the first test flight unrepresentative.
Is there an MSFS FPS booster that really works?
There is no universal MSFS FPS booster that can remove a genuine CPU, GPU or memory limit without a trade-off.
Some tools are useful because they automate an optimisation the user could perform manually. Automatic LOD utilities can reduce detail near demanding airports, frame-generation tools may improve displayed smoothness on supported systems, and add-on managers can help isolate content that is loaded unnecessarily. None creates free simulation performance.
- Choose an automatic LOD tool when performance varies sharply between cruise and airports and you accept visible draw-distance changes.
- Choose frame generation when base frame pacing is already stable and smoother presentation matters more than the small latency and artefact risk.
- Choose add-on management when a large content library causes conflicts, duplicated scenery or excessive loading.
- Avoid generic PC boosters that promise gains through registry cleaning, forced process priority, disabled security services or routine memory purging.
Our assessment of what MSFS performance utilities can and cannot improve explains the sensible uses and limitations of these tools.
Can aircraft and scenery add-ons reduce FPS?
Complex aircraft, detailed airports, traffic injectors and overlapping scenery can reduce FPS even when the graphics settings are appropriate.
- Temporarily remove Community content. Rename or move the active Community folder rather than deleting packages.
- Disable other installed packages. An empty Community folder does not disable content installed or managed through the simulator itself.
- Retest with stock content. Keep the airport, weather, stand and camera unchanged while substituting a simpler aircraft or airport.
- Restore add-ons in small groups. When the fault returns, divide that group until the responsible package or conflict is identified.
If only one airport performs badly, look for duplicate versions, overlapping city scenery or an old compatibility package. If only one aircraft is affected, its avionics, cabin modelling or systems simulation may be the main-thread workload; lowering resolution will not fix that.
What FPS should I target in Microsoft Flight Simulator 2024?
Target the highest frame rate the system can maintain during the demanding part of the flight, not its maximum in cruise.
A stable 30 or 40 FPS can feel better than an uncapped result that swings continuously between 40 and 70. On a fixed-refresh display with V-Sync, choose a cap that divides cleanly into the refresh rate. With variable refresh rate, choose a limit inside the display's supported range and below the point where the simulator repeatedly becomes unstable.
Test the cap at the destination airport, in the intended aircraft and weather. Capping FPS also reduces heat, fan noise and power consumption when the GPU would otherwise render frames that the display cannot use.
What changes on Xbox, PlayStation and in VR?
Console and VR users follow the same bottleneck logic, but they do not have all the diagnostic and graphics controls available on a conventional PC monitor.
Xbox Series X|S, PS5 and PS5 Pro
On console, use any quality or performance option exposed for that platform, reduce traffic and airport activity where available, and test without optional add-on content. Fully close and relaunch the simulator after persistent degradation rather than relying indefinitely on a suspended session.
PC-only driver profiles, Community-folder tools and most FPS booster utilities do not apply. If one aircraft or airport causes the problem, isolate that content in the same way as on PC; if every flight is affected, check cooling, storage space, online services and the simulator installation.
VR headsets
VR performance depends heavily on per-eye render resolution and the headset's refresh or reprojection cadence. Lower VR render resolution first for a GPU limit, and lower traffic and LOD for a main-thread limit. Monitor frame generation and VR reprojection are different technologies, so advice for one should not be applied blindly to the other.
What if sensible settings barely change performance?
If relevant settings produce almost no change, the simulator is capped, throttling, using the wrong hardware or limited somewhere outside that setting group.
- Confirm that the simulator is using the dedicated GPU rather than integrated graphics.
- Connect laptops to mains power and select an appropriate performance mode.
- Check CPU and GPU temperatures for clock-speed reductions caused by thermal throttling.
- Install the simulator, packages and cache on SSD storage with adequate free space.
- Leave the Windows page file system-managed; disabling it can turn memory pressure into instability.
- Check for frame caps in the simulator, graphics driver and third-party utilities.
- If render scaling changes nothing, return to main-thread load, traffic and external caps.
- If traffic and LOD changes do nothing, inspect GPU load, resolution, clouds and VRAM use.
When clean testing confirms a sustained hardware limit, lower the target frame rate or upgrade the component identified by the performance overlay. Configuration edits cannot create spare frame time once the limiting component is already fully occupied.