How do I improve FPS in any flight simulator?

To improve FPS in any flight simulator, first identify whether the main limit is the CPU, GPU, VRAM, RAM or scenery streaming. Test one repeatable flight, change one setting at a time, lower the options tied to that bottleneck, cap the frame rate for steadier frame times, and isolate add-ons and background software.

This method applies across Microsoft Flight Simulator, X-Plane, Prepar3D, FSX, DCS and FlightGear. There is no universal high-performance preset: a setting that helps a GPU-limited system may do almost nothing when the simulator is waiting for its main CPU thread.

How do I find what is limiting flight simulator FPS?

The quickest diagnosis is to compare CPU and GPU frame times while running the same demanding flight. Use the simulator's performance display where available; otherwise, use an operating-system or graphics-driver overlay showing FPS, GPU load, temperatures, RAM and VRAM.

1. Create a repeatable test. Use the same aircraft, airport, runway, weather, traffic, cockpit view and time of day. A complex airliner at a large airport is useful as a worst-case test, but also record a lighter general-aviation flight.
2. Remove the frame cap temporarily. V-Sync or another limiter can hide the real bottleneck by preventing FPS from rising. Restore a cap after testing.
3. Reduce render resolution sharply. If FPS rises substantially, the GPU is probably the limit. If performance barely changes, suspect the CPU, traffic, aircraft systems or scenery draw calls.
4. Check CPU and GPU frame times. The component with the longer frame time is determining the maximum FPS. Overall CPU utilisation can be misleading because one saturated main thread may limit the simulator while the other cores remain partly idle.
5. Test without add-ons. Load a default aircraft and airport with third-party scenery, traffic injectors, weather tools and cockpit utilities disabled. Reintroduce them in small batches.
6. Change one setting at a time. Record the result, restart the simulator when required, and repeat the identical test. Changing ten sliders together tells you nothing about which one helped.

Microsoft Flight Simulator users can follow our more detailed MSFS 2024 CPU, GPU and streaming diagnosis workflow. For X-Plane, the repeatable X-Plane 12 benchmarking method explains how to separate CPU and GPU limits on both Mac and PC.

Which graphics settings improve FPS the most?

The most effective settings are the ones assigned to the component that is actually limiting the simulator. Lowering texture quality on a CPU-bound machine, for example, usually sacrifices clarity without producing a meaningful frame-rate gain.

Settings to lower when GPU-limited

• Render resolution or render scaling: usually the strongest GPU control, especially at 4K or in VR.
• Anti-aliasing and supersampling: avoid applying high simulator scaling and additional headset or driver supersampling at the same time.
• Clouds, shadows and reflections: expensive in poor weather, near cities and around large airports.
• Ambient occlusion, lighting and post-processing: reduce these after resolution if image clarity matters.
• Texture resolution: lower it primarily when VRAM is under pressure; spare VRAM does not automatically mean more FPS.

Settings to lower when CPU-limited

• Terrain and object level of detail: longer draw distances create more objects and draw calls for the CPU to prepare.
• AI, road, airport and multiplayer traffic: each moving object may require simulation, animation and rendering work.
• Autogen or scenery density: particularly costly over large cities and detailed third-party airports.
• Glass-cockpit refresh rate: complex avionics and multiple displays can consume significant main-thread time.
• Aircraft and mission complexity: a heavily scripted airliner or combat mission may remain CPU-limited even with modest graphics settings.

Older simulators need different priorities. FSX, for example, is often constrained by its older CPU-heavy engine, so use the FSX-specific adjustments for autogen, traffic, weather and add-ons rather than copying settings intended for a modern renderer.

Why do flight simulator add-ons cause stutters?

Add-ons cause stutters when they add excessive objects, large textures, scripts, traffic, weather processing or overlapping scenery. A high-detail airport may run well alone but become troublesome when combined with a complex aircraft, live traffic and dense weather.

Disable all third-party content and test a default scenario first. If that fixes the problem, restore add-ons in batches until the slowdown returns, then test that batch individually. Watch for duplicate airports, overlapping terrain or mesh, outdated aircraft modules, traffic packages running alongside built-in traffic, and utilities polling the simulator too frequently.

A gradual performance decline during a long flight points more towards memory pressure or an add-on fault than an ordinary graphics setting. Restarting may clear the symptom, but isolating the responsible aircraft, scenery or utility is the real fix.

Should I cap my flight simulator frame rate?

A frame-rate cap improves smoothness when it is set to a rate the computer can sustain during demanding flights. A stable 30, 40 or 60 FPS often feels better than an uncapped rate constantly swinging above and below the display's synchronisation range.

Use the simulator limiter, display synchronisation or a driver limiter, but avoid stacking several limiters without a reason. Fixed-refresh displays generally work best with a cap compatible with their refresh rate, while a variable-refresh display can hide smaller fluctuations. Our guide to driver-level frame caps, V-Sync and variable refresh settings covers the interaction in more detail.

Frame generation can raise the displayed FPS, but it does not reduce the CPU work behind flight modelling, avionics or traffic. It also cannot repair severe base-frame stutter, and fast camera movement may reveal generated-frame artefacts. Establish a stable native frame rate before enabling it.

When will a hardware upgrade improve FPS?

A hardware upgrade helps only when it targets the measured bottleneck. Use the resolution test, frame-time readings and memory behaviour rather than choosing a component from average utilisation alone.

• Upgrade the graphics card when the GPU frame time is consistently higher and reducing resolution or GPU effects produces a large gain.
• Upgrade the CPU or platform when the main thread is limiting performance and reducing traffic, detail distance or aircraft complexity helps more than lowering resolution.
• Add RAM when the system is exhausting physical memory and paging during normal flights. Extra unused RAM does not increase FPS.
• Choose more VRAM when high-resolution textures, VR or detailed scenery exceed the graphics card's practical capacity.
• Move the simulator to an SSD to improve loading and reduce storage-related pauses. It normally will not raise average FPS when the CPU or GPU is already the limit.

Before buying hardware, check for thermal throttling, inadequate cooling, low-power modes and applications using the CPU or GPU in the background. On a laptop, connect mains power, select an appropriate performance profile and confirm that the simulator is using the dedicated GPU.

Which performance-tuning mistakes should I avoid?

The most common mistake we see is copying another simmer's settings without checking whether both systems share the same bottleneck. Resolution, display refresh, aircraft, airport, weather and add-ons can make apparently similar computers behave very differently.

• Do not judge performance from menus, loading screens or an empty rural flight when the real problem occurs at a major airport.
• Do not chase the highest average FPS while ignoring frame-time spikes; regular delivery of frames determines perceived smoothness.
• Do not delete shader caches repeatedly. The simulator or driver may need to compile shaders again, causing temporary stutters.
• Do not disable the operating system's page file as an optimisation; doing so can turn memory pressure into crashes.
• Do not apply undocumented configuration tweaks before establishing a clean baseline. Updates can make old tweaks ineffective or harmful.
• Do not assume every driver update improves performance. If a slowdown began immediately after a change, compare against the last known stable configuration.

Once the simulator delivers stable frame times in the repeatable test, validate the settings at a dense airport, in poor weather and during a longer flight. That final check prevents an impressive benchmark from becoming an unstable real-world configuration.