How do I fix FPS drops on landing in MSFS 2024?
FPS drops during landing in Microsoft Flight Simulator 2024 because the simulator must process a detailed airport, nearby traffic, ground activity, streamed scenery and complex cockpit systems at once. Fix it by identifying whether the main thread, GPU, VRAM or scenery streaming is responsible, then reducing that specific workload.
Why does FPS drop on final approach?
Landing combines several of MSFS 2024's heaviest workloads in one place, particularly at large handcrafted or add-on airports. The effect can be a steady frame-rate decline, uneven frame pacing or sharp pauses as new assets load.
- Airport detail: terminals, apron equipment, lighting, parked aircraft and ground vehicles increase object and draw-call counts.
- Traffic: live or AI aircraft, multiplayer models, road vehicles and airport activity put extra pressure on the main thread.
- Scenery streaming: photogrammetry, terrain and airport assets may arrive as the aircraft descends, causing hitches if the connection, cache or storage cannot keep up.
- Aircraft systems: complex avionics, glass displays and popped-out instrument windows can leave too little CPU headroom for the airport.
- GPU and VRAM pressure: clouds, high resolution, cockpit displays, large textures and detailed scenery can exceed the graphics card's comfortable workload.
How do I identify the landing bottleneck?
On PC, Developer Mode's FPS display is the quickest way to separate a main-thread limitation from a GPU limitation. Turn frame generation off temporarily while testing, because generated frames can disguise a weak base frame rate without removing the underlying stutter.
- Create a repeatable test. Use the same aircraft, runway, weather, traffic and camera view each time. Change only one setting category between runs.
- Watch the limiting component. Labels such as
Limited by MainThreadorLimited by GPUreveal which side needs attention. Total CPU usage can appear low even when the simulator's main thread is saturated. - Compare cockpit and exterior views. A large improvement outside the cockpit points towards avionics, display refresh rates or popped-out panels.
- Test simpler content. Fly a default light aircraft into a standard airport. Good performance there usually means the original aircraft, airport or traffic package is the problem.
- Compare a short and long flight. If spawning near the airport is smooth but arriving after a long sector is not, investigate VRAM or memory pressure and add-ons that accumulate load.
| Observed behaviour | Most likely cause | First adjustment |
|---|---|---|
| FPS falls as the airport comes into view | Main thread, airport objects or traffic | Lower Object LOD and traffic |
| GPU remains fully loaded during the approach | Resolution, clouds, shadows or reflections | Lower render scale or use an upscaler |
| Sharp pauses with delayed or changing scenery | Streaming, cache, storage or VRAM | Check the connection, cache and texture load |
| Only the cockpit is slow | Avionics or instrument windows | Reduce glass-cockpit refresh and close pop-outs |
| Only one airport is affected | Airport package, conflict or excessive local detail | Test the stock airport without add-ons |
For system-wide bottlenecks beyond the landing phase, use our wider MSFS 2024 performance checklist.
Which settings fix approach and landing FPS?
Lower the settings associated with the measured bottleneck rather than reducing everything. Dropping render scale will rarely fix a main-thread problem, while reducing traffic will not rescue a GPU overloaded by resolution and clouds.
If MSFS 2024 is main-thread limited
Main-thread limitations respond best to lower object density, traffic and cockpit processing.
- Reduce Objects Level of Detail first, followed by Terrain Level of Detail if the approach remains CPU-bound.
- Reduce AI or live traffic, multiplayer traffic, parked aircraft and airport ground activity. Test these separately to identify the expensive category.
- Lower Glass Cockpit Refresh Rate and close any popped-out instruments or extra simulator windows.
- Test without external traffic packages and highly detailed airport scenery.
If the GPU or VRAM is limiting performance
GPU-bound approaches need fewer pixels or lighter visual effects, while VRAM pressure calls for smaller texture and scenery loads.
- Reduce render scale modestly or choose the quality mode of the upscaler supported by the graphics card.
- Lower clouds, shadows, reflections and ambient occlusion before sacrificing all scenery detail.
- Reduce texture resolution if VRAM is near its limit or stuttering begins when airport textures load.
- Use frame generation only after the base frame rate is stable. It can improve displayed smoothness, but it does not cure main-thread stalls or streaming pauses.
Our hardware and graphics-setting breakdown for MSFS 2024 explains the trade-offs between render scale, LOD, clouds, traffic and cockpit displays. On Xbox Series X|S and PlayStation 5, fewer controls are exposed, so prioritise the available graphics choices, traffic reductions and add-on isolation.
If the problem is scenery-streaming hitching
Streaming problems usually appear as pauses or inconsistent frame times rather than a stable low frame rate.
- Stop background downloads and use a stable wired connection where possible.
- Delete and recreate the rolling cache if it appears corrupted, and keep it on fast storage with adequate free space where the platform permits this.
- Disable photogrammetry temporarily as a diagnostic test. If the pauses disappear, investigate connectivity and cache behaviour before leaving it disabled permanently.
- Do not assume that a larger rolling cache raises FPS; its main purpose is reducing repeated scenery downloads.
Persistent scenery loading problems are covered in our scenery-streaming and rolling-cache troubleshooting.
Why does it happen at only one airport?
A landing slowdown confined to one airport normally indicates unusually demanding scenery, duplicate airport packages or a conflict between installed content.
- Fly the same aircraft into a comparable stock airport.
- Test the affected airport with a simple default aircraft and traffic disabled.
- On PC, temporarily remove packages from the
Communityfolder. On console, disable optional airport, aircraft and traffic content through the simulator's content management controls. - Restore packages in small groups until the slowdown returns.
- Check for two packages modifying the same airport, including an older package carried across from MSFS 2020.
A detailed aircraft, high-density traffic and a large airport can each perform acceptably alone but overwhelm the main thread when combined. Our guide to aircraft, scenery and traffic add-on choices explains the compatibility and performance considerations.
How do I keep landing performance smooth?
Set your graphics target around the busiest airport you regularly use, not the frame rate seen at cruise altitude.
- Leave enough GPU and main-thread headroom before descent rather than running at the limit throughout cruise.
- Cap FPS at a rate the system can hold during final approach, or use variable refresh rate if the display supports it.
- Keep a separate preset for dense hubs, VR or complex airliners if one configuration cannot cover every flight.
- Re-test after simulator, graphics-driver or add-on updates because shader compilation and changed content can alter the result.
A restart that temporarily fixes performance is useful evidence of memory pressure or a misbehaving add-on, but it is not the permanent cure. Isolate the package or setting that causes the workload to grow during the flight.