Improve FPS in any flight simulator by finding CPU, GPU, VRAM or streaming limits, then changing the settings that actually cause slow frames.
To improve FPS in any flight simulator, first identify whether the main CPU thread, GPU, video memory, system memory, storage or scenery streaming is causing the slowest frames. Test one demanding flight repeatedly, alter one relevant setting at a time, remove faulty add-ons, then cap the frame rate at a level the system can sustain.
This advice applies to flight simulators in general, including Microsoft Flight Simulator, X-Plane, DCS, Prepar3D, FSX and FlightGear. Setting names and performance displays vary, but the underlying CPU, GPU and memory limits are much the same.
What does FPS mean in a flight simulator?
FPS means frames per second, the number of complete images the simulator presents each second. Frame time is the more useful diagnostic measurement because it reveals irregular slow frames that an average FPS figure can hide.
At 30 FPS, each frame has about 33.3 milliseconds to complete; at 60 FPS, it has about 16.7 milliseconds. A steady 30 FPS can therefore feel better than an average of 50 FPS that repeatedly drops or pauses. When a simulator reports that it is limited by the main thread or GPU, it is identifying which side has the longer frame time.
How to increase FPS while you fly
The reliable way to increase flight simulator FPS is to reproduce the slowdown and test one possible cause at a time.
- Create a demanding test flight. Use the same aircraft, airport, runway or parking position, weather, traffic, time of day and cockpit view. Test at the detailed airport where performance is poor, not over empty countryside.
- Display FPS and frame time. Use the simulator's developer or performance display where available. Overall CPU utilisation is misleading because one main simulation thread can be saturated while the remaining cores are lightly loaded.
- Remove frame-rate limits temporarily. On PC, disable V-Sync and other caps during diagnosis if the simulator permits it. A cap can conceal spare performance or make GPU utilisation appear lower than expected.
- Perform a resolution test. Reduce render scale or output resolution substantially. A clear FPS increase indicates a GPU limit; little or no change points towards the CPU, aircraft systems, traffic or scenery draw calls.
- Test default content. Repeat the flight with a default aircraft and airport, then disable third-party scenery, traffic tools, weather utilities and cockpit applications. This separates an add-on problem from a simulator-wide limit.
- Change one setting and repeat. Record the result, including stutters rather than just average FPS. Restart the simulator when a setting or add-on requires it.
| What happens during the test | Likely limit | Change first |
|---|---|---|
| Lower resolution produces a large FPS gain | GPU processing | Render scale, anti-aliasing, clouds, shadows and reflections |
| Lower resolution barely changes FPS | CPU or main thread | Traffic, object distance, scenery density and cockpit display refresh |
| Turning the camera causes sharp pauses | VRAM or asset loading | Texture resolution, high-resolution add-ons and scenery coverage |
| Pauses begin when system memory is nearly full | RAM pressure and paging | Background applications and memory-heavy add-ons |
| Stutters occur as new terrain appears | Storage, network or scenery streaming | Installation drive, connection stability and streaming options |
| Only one aircraft or airport performs badly | Content-specific workload | Test that aircraft, airport and overlapping add-ons separately |
For a worked modern example, our MSFS 2024 bottleneck diagnosis shows how to separate main-thread, GPU, VRAM and streaming problems before changing settings.
What are the best graphics settings for more FPS?
The best graphics settings lower the workload that is actually limiting the simulator while preserving options that have little effect on that bottleneck. An all-low preset often sacrifices cockpit and runway clarity without fixing a CPU-limited frame rate.
| Setting | Main performance cost | When to lower it |
|---|---|---|
| Render scale or output resolution | GPU | When the GPU frame time is highest and lower resolution improves FPS |
| Anti-aliasing or supersampling | GPU | When high render resolution or additional headset scaling is already active |
| Clouds, shadows and reflections | Mostly GPU, sometimes CPU | When FPS falls in poor weather, at night or around reflective surfaces |
| Terrain and object level of detail | CPU, with some GPU and memory cost | When dense airports and cities are main-thread limited |
| Autogen and scenery density | CPU and memory | When large numbers of buildings, trees or airport objects cause slow frames |
| AI, multiplayer, road and airport traffic | Mostly CPU | When performance is worst on the ground or around busy hubs |
| Cockpit display refresh | CPU and GPU | When a glass cockpit is much slower than an external view |
| Texture resolution | VRAM capacity | When VRAM fills and camera movement causes stutters |
| Anisotropic filtering | Usually a small GPU cost | Lower it late; it helps keep runways and ground textures sharp at an angle |
Texture quality is not a universal FPS slider. Lowering it helps when VRAM is under pressure, but may only make the cockpit blurry when the CPU or GPU processing cores are the true limit. Our setting-by-setting graphics quality guide covers resolution, anti-aliasing, textures, clouds, shadows and scenery detail in more depth.
Does lowering resolution increase FPS?
Lowering resolution increases FPS when the GPU is the limiting component, but it does little for a main-thread bottleneck. Where supported, keep the display at its native resolution and reduce the simulator's render scale or use its built-in upscaler; menus and cockpit text usually remain clearer this way.
A typical 4K display contains four times as many pixels as 1080p, so changing to 4K can turn a balanced system into a GPU-limited one. In VR, check both the simulator render scale and the headset software scale. Applying supersampling in both places is a common cause of unexpectedly low flying FPS.
Should I use V-Sync, a frame cap or frame generation?
Use one frame limiter after tuning, set to a rate the simulator can maintain in demanding conditions. Stacking an in-simulator cap, a driver cap and V-Sync can produce uneven pacing or unnecessary input delay.
On a fixed 60 Hz display, a stable 30 or 60 FPS target usually paces better than a rate that continually crosses the display's refresh boundary. Variable-refresh displays offer more flexibility, provided the frame rate remains inside their supported range.
Frame generation can raise the displayed FPS, but it does not reduce the CPU work required for flight modelling, avionics, traffic or scenery preparation. Establish stable native frame delivery first; generated frames cannot repair severe base-frame stutter and may show artefacts during fast camera movement.
Do the same settings work in MSFS, X-Plane, DCS and FSX?
The same diagnostic method works across simulators, but the most expensive settings differ by engine and version. Modern simulators may combine detailed glass cockpits, streamed scenery and advanced rendering, while older engines can remain dominated by one CPU thread even with a capable graphics card.
FSX users should not copy a modern MSFS preset. Autogen, AI traffic, clouds, water effects and CPU-heavy add-ons need different priorities, as explained in our FSX-specific performance advice.
Why is flight simulator FPS low only at airports or in bad weather?
Airports and bad weather combine the simulator's heaviest CPU, GPU and memory workloads, so they expose limits that remain hidden during cruise. Detailed buildings, parked aircraft, ground vehicles, traffic, cockpit systems, cloud layers, shadows and reflections may all be active together.
- Slow only at busy airports: reduce traffic, object level of detail and airport clutter first.
- Slow only in thick cloud: reduce cloud quality, shadow quality or render resolution.
- Slow only inside one aircraft: test cockpit display refresh, avionics complexity and aircraft-specific add-ons.
- Slow only at one third-party airport: check for duplicate or overlapping scenery and compare it with the default airport.
- Slow after a long flight: inspect memory use, temperatures and clock speeds rather than assuming the initial graphics settings are wrong.
Always tune for the demanding phase you actually fly. Settings that produce 80 FPS in cruise are not useful if the same system falls below the chosen target during approach.
Why does the simulator stutter even when FPS is high?
High average FPS with visible stutters usually indicates uneven frame delivery, asset loading, shader compilation, memory pressure or an add-on fault. Average FPS can remain respectable even when occasional frames take several hundred milliseconds.
- Camera-turn stutters: suspect VRAM overflow, large textures or scenery assets being loaded.
- Stutters when entering a new area: suspect scenery streaming, storage access or network delivery.
- Stutters after a driver or simulator update: shaders may be compiling again; repeated cache deletion can make this worse.
- Stutters that grow during a flight: watch RAM, VRAM, temperatures and add-ons whose memory use keeps rising.
- Regular pauses at fixed intervals: disable traffic injectors, recording tools, weather utilities and other applications that poll or update the simulator.
To isolate third-party content, disable it all, confirm that the test flight is smooth, then restore items in small batches. Test individual items from the first batch that brings the problem back. Duplicate airports, overlapping terrain, two traffic systems and outdated aircraft modules are frequent causes.
An SSD can shorten loading and reduce pauses caused by slow asset delivery, but it rarely increases average FPS when the CPU or GPU is already limiting performance. See our explanation of what an SSD can and cannot improve before treating storage as a frame-rate upgrade.
What FPS is good for a flight simulator?
A stable 30 FPS is usable for most aviation simulation, while stable 40 or 60 FPS gives smoother camera movement and control response when the hardware can sustain it. Consistent frame time matters more than a high average that collapses at airports.
- 30 FPS: about 33.3 milliseconds per frame and a practical target for complex aircraft or modest hardware.
- 40 FPS: 25 milliseconds per frame and useful with a compatible variable-refresh display.
- 60 FPS: about 16.7 milliseconds per frame, with much greater CPU and GPU demand.
VR is different because the headset has its own refresh and reprojection targets. Use a supported native or reprojection rate rather than applying the desktop 30 FPS guideline blindly.
Will a hardware upgrade increase FPS?
A hardware upgrade increases FPS only when it removes the measured bottleneck. Buying more RAM, VRAM or storage does not automatically make a CPU-bound simulator render frames faster.
- Upgrade the GPU when reducing render resolution produces a clear gain and GPU frame time remains highest.
- Upgrade the CPU or platform when lowering traffic, object distance or aircraft complexity helps more than lowering resolution.
- Add system RAM when normal flights exhaust physical memory and begin paging. Extra unused capacity does not raise FPS.
- Choose more VRAM when detailed airports, high-resolution textures or VR repeatedly exceed graphics-memory capacity. Spare VRAM alone does not provide more processing speed.
- Use faster storage for loading and asset-delivery pauses, not as a general cure for low average FPS.
How do I improve FPS on a laptop or console?
On a laptop, use mains power, select the appropriate performance profile, confirm that the dedicated GPU is running the simulator and keep the cooling vents unobstructed. Falling clock speeds after several minutes indicate thermal or power throttling rather than a graphics-setting problem.
High-resolution laptop panels can overload a modest mobile GPU, so perform the resolution test before cutting texture quality. An under-rated charger or dock may also prevent the CPU and GPU from sustaining their intended power levels.
On a console, CPU, GPU and VRAM allocation cannot be upgraded or tuned through drivers. Use any performance or quality mode provided by the simulator, reduce traffic or online scenery options where available, and remove add-ons linked to repeatable stutters.
Which FPS fixes should I avoid?
Avoid tweaks that alter reported numbers or system behaviour without addressing CPU time, GPU time or memory pressure.
- Do not use registry edits that claim to create dedicated VRAM.
- Do not disable the operating system page file; memory pressure may become a crash instead of a slowdown.
- Do not delete shader caches routinely, because rebuilding them can introduce fresh stutters.
- Do not force process priority or CPU affinity changes without simulator-specific evidence that they help.
- Do not copy another simmer's complete preset without matching their resolution, aircraft, airport, weather and add-ons.
- Do not judge success by the highest FPS seen in cruise; inspect the slowest frame times in the demanding test.
Validate the final settings at a detailed airport, in poor weather and during a longer flight. The useful configuration is the one that remains smooth where you actually fly, not the one that produces the largest FPS figure in an easy scene.