Learn when a flight simulator FPS cap improves smoothness, how to choose 30, 40 or 60 FPS, and when V-Sync, VRR or a VR target works better.
Yes—cap frame rate in a flight simulator when uncapped FPS fluctuates, causes uneven frame times, or needlessly drives the GPU at full load. Set the cap to a rate your PC can sustain at demanding airports: usually 30 FPS for 60 Hz displays, or 40 FPS on 120 Hz displays.
What flight simulator FPS cap should I use?
Use the highest cap that remains stable in your heaviest normal scenario, not the peak FPS seen while cruising over empty terrain. This principle applies across Microsoft Flight Simulator, X-Plane, Prepar3D and FSX, although older simulators respond differently to their internal limiters.
| Display setup | Recommended starting point | Reason |
|---|---|---|
| 60 Hz fixed-refresh monitor | 30 FPS, or 60 FPS if consistently sustainable | Both divide evenly into 60 Hz; an unstable 40 FPS can produce uneven cadence without VRR. |
| 120 Hz fixed-refresh monitor | 30, 40 or 60 FPS | Each divides evenly into 120 Hz, producing consistent frame presentation. |
| Other fixed-refresh monitor | An exact divisor of its refresh rate | Examples include 25 FPS at 75 Hz and 36, 48 or 72 FPS at 144 Hz. |
| VRR display | The highest rate sustainable in demanding conditions | VRR accommodates changing frame rates within its operating range. If performance approaches the display ceiling, cap a few frames below it. |
| VR headset | A native refresh rate or supported reprojection fraction | The headset runtime controls cadence; a desktop-monitor cap may conflict with it. |
At 30 FPS, each frame takes 33.3 milliseconds; at 40 FPS it takes 25 ms, and at 60 FPS it takes 16.7 ms. Thirty is often adequate for airliner operations, while 40 or 60 noticeably improves cockpit panning, low-level flying, helicopters and rapid control inputs.
Avoid choosing an extremely low limit merely to make the graph flat. Low frame rates increase input latency, and some simulators can reduce simulation speed when performance falls below their usable minimum.
How do I find the right frame-rate limit?
The right limit comes from the lowest sustained performance in a representative flight, with a small margin left for weather, traffic and complex scenery.
- Create a demanding test: load a detailed aircraft at a busy airport, add the weather and traffic levels you normally use, then test both the ground and approach phases.
- Measure frame time as well as FPS: a steady 35 FPS can feel better than a counter oscillating between 40 and 60. MSFS users can follow our explanation of displaying FPS, frame time and CPU/GPU bottlenecks.
- Find the sustained floor: ignore a single loading pause, but account for recurring drops. For example, if the simulator usually varies between 43 and 52 FPS, try 40; if it sits between 32 and 38, use 30.
- Match the display cadence: on a fixed-refresh monitor, prefer a rate that divides evenly into the refresh rate. VRR users have more freedom.
- Apply one limiter and retest: repeat the same flight and compare panning, taxiing, frame-time spikes, temperature and fan noise. A repeatable MSFS benchmark procedure makes before-and-after results more reliable.
Should I use V-Sync, VRR or an FPS limiter?
Use VRR when available, V-Sync when tearing is the main problem, and a frame limiter when you need a stable performance ceiling or lower hardware load.
- In-simulator limiter: start here when the simulator provides a target frame-rate setting and its frame pacing is consistent.
- GPU driver limiter: use this when the simulator has no suitable limiter or its built-in option produces poor pacing.
- V-Sync: synchronises frames with the display and removes tearing, but can add latency or cause abrupt cadence changes when the PC cannot maintain the selected rate.
- VRR: lets the monitor follow the simulator within its supported range, reducing tearing and judder without forcing every frame into a fixed refresh interval.
Do not stack an in-simulator cap, a driver cap and multiple V-Sync controls without a specific reason. Competing limiters can create erratic frame times and make troubleshooting much harder. A limiter by itself also does not guarantee tear-free output on a fixed-refresh display.
Can an FPS cap improve scenery loading or stop stutters?
A cap can provide processing headroom and improve frame pacing, but it cannot fix every source of stuttering. Shader compilation, storage delays, excessive traffic, complex add-ons and scenery conflicts can still produce pauses below the chosen limit.
FSX is a notable case: its internal target frame-rate setting can leave more processing time for scenery and texture loading than Unlimited. A sustainable target around 20–30 FPS is often preferable; our FSX limiter and performance guidance explains why the best number depends on scenery and aircraft complexity.
In newer simulators, capping an otherwise saturated GPU can create useful headroom. If the simulator is already limited by its main CPU thread and cannot reach the cap, however, the limiter changes nothing. MSFS 2024 users should instead apply settings matched to the actual CPU or GPU bottleneck.
What changes in VR or with frame generation?
VR and frame generation require cadence-aware settings rather than a generic desktop FPS cap. In VR, select a headset refresh rate the system can hold, or use a supported reprojection mode such as half-rate operation; manage this through the headset runtime rather than an unrelated monitor limiter.
With frame generation enabled, the displayed FPS includes generated frames, while aircraft response still depends heavily on the lower rendered base rate. Limiter behaviour can also differ depending on whether it acts before or after generated frames are inserted. Check both base performance and perceived latency, then use only the limiter that produces consistent frame times.
For a practical first test, use 30 FPS on a 60 Hz display, 40 FPS on a 120 Hz display, or 60 FPS when the simulator can hold it during the most demanding part of the flight. Adjust from that measured result rather than chasing the highest number shown in easy conditions.