Variable Refresh Rate (VRR) Configuration Matrix
| Setting Combination | Screen Tearing at Max Hz? | Input Lag Penalty | VRR Window Maintained? | Recommendation Status |
|---|---|---|---|---|
| G-Sync ON + V-Sync OFF (No Cap) | YES (Severe tearing at screen bottom) | Minimal (0 ms) | NO (Breaks out of VRR range when FPS >= Max Hz) | Flawed common myth; causes tearing |
| G-Sync ON + V-Sync ON (No Cap) | NO | Massive (+16 ms to +32 ms traditional V-Sync buffer) | NO (Engages legacy V-Sync backpressure when capped) | High input lag; feels sluggish |
| G-Sync ON + V-Sync OFF + Cap (-3 FPS) | YES (Occasional tear line near bottom scanout) | Minimal | Marginal (Frame delivery jitter momentarily exceeds cap) | Acceptable but imperfect |
| G-Sync ON + Driver V-Sync ON + Reflex / Cap (-3 FPS) | ZERO TEARING | Absolute Lowest Latency (Below 3 ms) | 100% Locked inside VRR range continuously | GOLD STANDARD (Blur Busters Verified) |
A persistent misconception among PC gamers is that enabling Vertical Sync (V-Sync) alongside NVIDIA G-Sync or AMD FreeSync causes input lag or is completely redundant. Extensive high-speed camera testing by Blur Busters proved the opposite: without driver-level V-Sync and an FPS cap set strictly 3 to 4 frames below your monitor's maximum refresh rate, variable refresh rate modules fail to eliminate tearing across the lower scanout area.
Phase 1: The Physics of the VRR Ceiling and Scanout Tears
- The Instantaneous Frequency Overshoot: If you play on a 144 Hz display and cap your framerate in-game to exactly 144 FPS, frame delivery variance means individual frame times will fluctuate between 6.8 ms and 7.1 ms. The moment a single frame renders faster than
1 / 144seconds (6.94 ms), instantaneous framerate spikes to 145+ FPS. - Dropping Out of the G-Sync Module Range: G-Sync only operates below the panel's maximum refresh rate. The millisecond FPS hits or exceeds 144, the hardware module disengages:
- If V-Sync is OFF, a tear line immediately appears on the lower third of the display.
- If V-Sync is ON, the GPU pauses render submission, triggering traditional double-buffer V-Sync backpressure and injecting 1 to 2 frames of input lag.
- The Minus-3 FPS Safety Margin: Setting your frame cap to 141 FPS (on 144 Hz), 162 FPS (on 165 Hz), or 237 FPS (on 240 Hz) guarantees that natural frame delivery jitter never penetrates the ceiling of the VRR operation window.
Phase 2: The Universal Three-Rule Implementation
Configure these exact parameters for flawless, tear-free, minimum-lag rendering:
1. In NVIDIA Control Panel / AMD Adrenalin:
- G-Sync / FreeSync: Enabled for Full Screen Mode.
- Vertical Sync: Set to On in global driver settings. (Driver V-Sync acts as an automated frame pacing synchronizer, not an old-school buffer).
- Low Latency Mode: Set to Ultra (or enable Reflex inside supported games). Ultra automatically applies the required (-3 FPS) frame limiter.
2. In In-Game Settings:
- In-Game V-Sync: Set to Off. (Let the driver handle synchronization).
- In-Game Frame Limiter: If the game does not support NVIDIA Reflex, set the in-game limiter or RTSS limiter to:
- 144 Hz Monitor: Cap at
141 FPS - 165 Hz Monitor: Cap at
161 FPS - 240 Hz Monitor: Cap at
236 FPS - 360 Hz Monitor: Cap at
352 FPS
- 144 Hz Monitor: Cap at
Verification Checklist
- Run a panning camera test in a fast-paced game; confirm absolute zero horizontal tear lines.
- Monitor frametimes via RivaTuner Statistics Server (RTSS); confirm the green frametime graph forms a ruler-flat horizontal line.
- Verify G-Sync indicator (enabled via NVIDIA Control Panel Display menu) remains illuminated throughout gameplay.