Learn what counts as good FPS for a flight simulator, why stable 30 FPS feels smooth, and when to target 40–60 FPS or a VR refresh rate.
For most flight simulators, a stable 30 FPS is good and 40–60 FPS feels very smooth. Consistent frame times matter more than a high average: locked 30 FPS without stutters usually feels better than 60 FPS that repeatedly drops. In VR, aim for the headset’s supported refresh rate or a stable reprojection target.
This applies broadly to Microsoft Flight Simulator 2020 and 2024, X-Plane, Prepar3D and FSX. The best target changes with the aircraft, scenery, display and type of flying, so there is no single number that suits every setup.
What flight simulator FPS should you target?
| Frame rate | Typical experience | Best use |
|---|---|---|
| Below 20 FPS | Noticeably rough, with delayed controls and jerky camera movement | Usually needs settings or add-on troubleshooting |
| 20–29 FPS | Playable, but panning and low-level flight may look uneven | Complex aircraft, large airports or older simulators |
| 30–39 FPS | Good when frame delivery is consistent | Airliner flying, instrument procedures and general desktop use |
| 40–59 FPS | Smooth and responsive | A strong practical target for modern flight simulators |
| 60 FPS or higher | Very smooth if the simulator can sustain it | Fast jets, aerobatics, low-level flying, external views and head tracking |
Older simulators should not be judged by modern performance expectations. In FSX, a stable 25–30 FPS can provide a better result than an unlocked rate that jumps between 20 and 60; our FSX tuning advice for holding a steady frame rate explains the simulator-specific trade-offs.
Is 30 FPS enough for a flight simulator?
Yes, a properly paced 30 FPS is enough for most conventional flying. Airliners, general aviation and instrument approaches do not demand the response times of a competitive action game. Thirty FPS also gives the CPU more time to process traffic, aircraft systems, scenery and flight-model calculations.
At 30 FPS, each frame takes about 33.3 milliseconds; at 60 FPS, it takes about 16.7 milliseconds. That advantage becomes obvious during rapid camera pans, head tracking, formation flight and low-level manoeuvring, but it matters less while cruising in a stable cockpit view.
A 30 FPS cap works particularly well on a 60 Hz or 120 Hz display because each frame can be shown for an equal number of refresh cycles. On a fixed-refresh monitor, an awkward mismatch between frame rate and refresh rate can introduce judder even when the FPS counter looks acceptable.
Why can high FPS still look choppy?
High average FPS can still look rough when individual frames arrive unevenly. A simulator alternating between 12 ms and 45 ms frame times may report a respectable average while producing visible hitches.
- Main-thread spikes: AI traffic, complex avionics, airport objects and scenery draw calls can briefly overload the CPU.
- Scenery loading: Terrain, photogrammetry, add-ons or online data may produce pauses as new areas are loaded.
- Memory pressure: Exhausted VRAM or system RAM can cause texture swapping and severe frame-time spikes.
- Display mismatch: V-Sync, an unsuitable frame cap or leaving the variable-refresh range can create uneven motion.
- Frame generation: Generated frames can improve visual fluidity, but they do not give 30 rendered FPS the control response of native 60 FPS. Some counters also report generated and rendered frames differently.
When the number appears healthy but motion does not, use our diagnosis for flight simulators that feel choppy at high FPS rather than lowering every graphics option indiscriminately.
Should you cap flight simulator FPS?
An FPS cap is useful when the simulator can hold that target during demanding flights. It reduces large performance swings, unnecessary GPU load, heat and fan noise while often improving frame pacing.
- Test a demanding situation. Use a complex aircraft at a large airport with representative weather and traffic, not an empty aircraft at cruise altitude.
- Measure frame times as well as FPS. In Microsoft Flight Simulator, reading the built-in FPS and frame-time information helps identify whether the main thread or GPU is limiting performance.
- Choose a sustainable target. Set the limit below the lowest frame rate your normal worst-case flight can maintain. A steady 30 or 40 FPS is preferable to targeting 60 and repeatedly missing it.
- Adjust the actual bottleneck. Traffic, terrain detail and object density often affect the CPU; resolution scaling, clouds, shadows and anti-aliasing usually place more load on the GPU. Our MSFS graphics-setting guidance for stable frame delivery covers those choices without treating every setting alike.
Variable refresh rate gives more freedom because the display can follow changing FPS within its supported range. Without it, use a frame cap and synchronisation arrangement that divides cleanly into the monitor refresh rate where possible.
What FPS should you target in VR?
In VR, target the headset’s native refresh rate or a stable supported fraction using reprojection. Head movement exposes missed frames far more clearly than a fixed monitor, so consistency and available performance headroom are essential.
For example, a headset running at 90 Hz may produce a smoother experience at a locked 45 rendered FPS with reprojection than at an unstable rate fluctuating between 55 and 80 FPS. Exact refresh rates and reprojection targets depend on the headset and runtime, and reprojection can introduce artefacts around propellers, wings and cockpit edges.
For desktop flying, start with 30 FPS as the minimum stable target and aim for 40–60 FPS when the hardware allows it. Increase the target for rapid head movement or low-level flying; lower it only when doing so removes frame-time spikes rather than merely improving the average counter.