Learn when a 30 FPS cap helps X-Plane 12 on a 60 Hz monitor, why V-Sync is still needed, and how to fix stutter without conflicts.
Yes—on a fixed-refresh 60 Hz monitor, capping X-Plane 12 at 30 FPS can reduce uneven frame pacing if the simulator can hold 30 consistently. Because 30 divides evenly into 60, each frame can occupy two refresh cycles. The cap alone does not eliminate screen tearing; V-Sync or another synchronisation method is still required.
When does a 30 FPS cap help X-Plane 12?
A 30 FPS cap works best when uncapped performance fluctuates above 30 but cannot remain near 60 FPS. A steady 30 often looks smoother than constant movement between 35 and 55 FPS, and the unused rendering headroom can soften smaller CPU or GPU workload spikes.
| Performance and display | Recommended approach |
|---|---|
| Fixed 60 Hz, usually 35–55 FPS | Cap at 30 FPS and enable synchronisation. |
| Fixed 60 Hz, reliably reaches 60 FPS | Target 60 FPS instead for smoother camera movement and lower latency. |
| Frequently falls below 30 FPS | Reduce the limiting graphics or CPU settings before applying a cap. |
| 60 Hz monitor with working variable refresh | Use VRR with a sustainable limit inside the display's supported range; 30 FPS is not automatically the best target. |
| Fast low-level flying or helicopters | Prefer a higher stable target if the hardware can maintain it. |
Thirty FPS gives each frame about 33.3 ms. X-Plane's CPU and GPU frame times should both remain comfortably below roughly 0.033 s in demanding weather, at complex airports and inside detailed cockpits. If either value repeatedly exceeds that budget, the cap cannot prevent dropped frames.
Our guidance on reading X-Plane's CPU and GPU frame times helps identify which settings are limiting performance. For other refresh rates and target values, see our broader guide to choosing a sustainable flight-simulator FPS limit.
Does a 30 FPS cap stop screen tearing?
No, an FPS cap controls rendering rate but does not guarantee that frames are presented during the monitor's refresh interval. Screen tearing is the visible horizontal split created when the display scans parts of different frames, so a synchronisation method is still needed.
- Fixed-refresh 60 Hz: use a 30 FPS limiter with V-Sync enabled in either X-Plane or the graphics driver.
- Half-refresh synchronisation: where the driver offers a suitable half-refresh mode, it can establish the required 30-on-60 cadence without conflicting presentation settings.
- G-SYNC or FreeSync: verify that 30 FPS falls inside the monitor's effective VRR range or is covered by low-framerate compensation. Otherwise, VRR may disengage at 30.
Fast Sync is generally the wrong choice here because it is intended for rendering rates above the monitor's refresh rate, not 30 FPS on a 60 Hz panel. V-Sync can also add some control latency, which is more noticeable during rapid manoeuvres than in a steady airliner cruise.
How should I cap X-Plane 12 at 30 FPS?
Set one frame limiter and one synchronisation policy, then test them in a demanding, repeatable flight. Running several limiters or forcing contradictory driver and simulator settings can create the very pacing problem the cap was meant to remove.
- Confirm the refresh rate. Check that the operating system or graphics driver has the intended display set to 60 Hz, particularly on a multi-monitor system.
- Measure the worst case. Use X-Plane's performance display at a heavy airport, with representative clouds, traffic, aircraft systems and plug-ins. The simulator should remain above 30 FPS with some margin before you lock it.
- Apply one 30 FPS limit. Use a per-application graphics-driver limit where available. NVIDIA users can follow our explanation of the per-program NVIDIA cap, V-Sync and G-SYNC controls. Equivalent setting names vary across other drivers and operating systems.
- Enable one sync method. On a fixed 60 Hz display, use V-Sync in either the simulator or driver rather than forcing incompatible policies in both places.
- Check frame delivery. Pan across the cockpit, turn on the ground and repeat the test in poor weather. Look for actual horizontal tearing, isolated pauses and sustained drops below 30 rather than judging only the average FPS counter.
If a VRR display can follow X-Plane between roughly the mid-range and 60 Hz, a sustainable limit within that range will usually feel more responsive than forcing 30. Keep the limit below the VRR ceiling and within the monitor's documented operating range; exact limits differ by display.
Why can X-Plane 12 still stutter at a locked 30 FPS?
A locked FPS counter cannot hide an occasional long frame, and not every visible pause is caused by frame-rate variation. The common causes are scenery loading, plug-in activity, CPU spikes, VRAM pressure and competing frame-control settings.
- Regular judder while panning: 30 FPS has lower temporal resolution than 60 FPS, so some stepping during rapid camera movement is normal rather than a fault.
- Drops to 29 FPS or lower: the CPU or GPU is missing the 33.3 ms budget; reduce the setting affecting the slower frame-time figure.
- Single sharp pauses: investigate scenery, aircraft systems, plug-ins and memory use instead of lowering the cap further.
- Tearing at a steady 30: the limiter is working, but V-Sync or VRR is not controlling presentation correctly.
- Rhythmic microstutter: disable duplicate limiters and retest with only one cap and one synchronisation method.
If the pauses remain after removing the cap and testing a clean configuration, use our process to diagnose plug-ins, scenery loading, VRAM pressure and other recurring hitches. A 30 FPS cap is a frame-pacing tool, not a substitute for fixing a workload that cannot sustain 30 FPS.