All Tool Comparisons
SIDE-BY-SIDE TELEMETRY COMPARISON • UNCAPPED FPS / DYAC 2

G-Sync / FreeSync (-3 FPS Rule) vs DyAc 2 / ULMB 2 vs Uncapped 360Hz+ FPS (2026)

TL;DR — Benchmark Verdict (Uncapped FPS / DyAc 2 vs Native OS Tuning)

For Variable Refresh Rate (G-Sync / FreeSync), the gold-standard telemetry rule is: VRR ON + Driver V-Sync ON (In-Game V-Sync OFF) + FPS Cap 3–5% below max Hz (e.g. 237 FPS on 240Hz, or Reflex's auto-cap ~225 FPS), yielding zero tearing and sub-millisecond sync overhead. By contrast, BenQ DyAc 2 / ULMB 2 backlight strobing delivers unmatched tracking clarity in CS2/Valorant when paired with steady FPS >= refresh rate, while Uncapped 360Hz–540Hz FPS minimizes raw input latency at the cost of slight tearing.

Feature / Telemetry MetricUncapped FPS / DyAc 2Clean Native Windows 10/11 Tuning
Display Sync Latency Overhead (240Hz Test)Uncapped 400 FPS: ~0.0ms sync overhead (micro-tearing)G-Sync + Driver V-Sync + 237 Cap: <0.3ms delta
Screen Tearing & Frame-Time FluctuationVisible tearing when FPS crosses Hz; DyAc stutters if FPS < HzZero tearing across 48–237 FPS range (VRR)
Fast-Pan Motion Clarity (UFO / Flick Tracking)DyAc 2 / ULMB 2 strobing = CRT-like sharpnessOLED 240–480Hz VRR closes gap; IPS VRR blurs more
Recommended FPS Cap FormulaUncapped or 2x Hz (DyAc requires FPS >= Hz)Max Hz - 3 (144–240Hz) or Hz - Hz²/3600 (225@240Hz, 324@360Hz)
Correct V-Sync Placement for VRRIn-Game V-Sync ON (adds input buffer if uncapped)Driver V-Sync ON + In-Game V-Sync OFF + FPS Cap
Best Competitive Genre FitDyAc 2 / Uncapped -> CS2, Valorant (300–500+ FPS)VRR (-3 Cap) -> Warzone, Apex, Fortnite, Finals

Engineering Verdict

Choose based on whether your FPS is rock-solid above your monitor's refresh rate. In variable-FPS games (Warzone, Apex, Fortnite, Tarkov), G-Sync/FreeSync + Driver V-Sync ON + a -3% FPS cap (or Reflex auto-cap) gives tear-free, low-latency aiming. In ultra-high-FPS tactical shooters (CS2, Valorant on 240–540Hz), either DyAc 2 / ULMB 2 (if you never dip below Hz) or Uncapped FPS + Reflex delivers the snappiest possible response.

Step-by-Step Practical Native Setup Guide

STEP 01

1. Apply the BlurBusters G-Sync / FreeSync Golden Rule

Enabling V-Sync in the driver while capping below refresh rate keeps G-Sync active 100% of the time without V-Sync backpressure. For 144Hz–240Hz manual caps, -3 FPS (141 @ 144Hz, 237 @ 240Hz) works cleanly; however at 240Hz–360Hz+, -3 FPS leaves almost zero time headroom (357 FPS = 0.023ms), so NVIDIA Reflex + VRR automatically scales by `Hz - (Hz² / 3600)` (~225 FPS @ 240Hz, ~324 FPS @ 360Hz).

Command / Path / Setting
NVIDIA CP: G-Sync ON (Fullscreen) + Vertical Sync = ON + Max Frame Rate = (Hz - 3 or Reflex Dynamic Cap) | In-Game V-Sync = OFF
STEP 02

2. Configure AMD FreeSync + Radeon Chill / FRTC Correctly

Prefer an in-game FPS limiter or RTSS set to (Hz - 3) over driver-level FRTC for the flattest frame-time line and lowest input delay under FreeSync.

Command / Path / Setting
AMD Adrenalin -> Gaming -> Display -> FreeSync: Enabled + Global Graphics -> Wait for Vertical Refresh: Always On + RTSS/In-Game Cap = (Hz - 3)
STEP 03

3. Configure DyAc 2 / ULMB 2 Backlight Strobing Without Double-Images

Backlight strobing turns off VRR on most TN/IPS panels (except G-Sync Pulsar). If your FPS drops below your strobed refresh rate (e.g., 190 FPS at 240Hz), strobe crosstalk and double-ghosting appear immediately—disable DyAc if you cannot sustain FPS >= Hz.

Command / Path / Setting
Monitor OSD: DyAc 2 / ULMB 2 = ON (disables VRR) + In-Game FPS >= Monitor Hz (e.g. 240+ FPS on 240Hz, or cap at exact 240)
STEP 04

4. Verify Monitor Refresh Rate & Color Depth in Windows Display Settings

After GPU driver updates or DisplayPort cable swaps, Windows frequently resets high-refresh panels back to 60Hz or 144Hz. Run this check to confirm Current Mode reports your monitor's full native Hz (e.g., 240Hz or 360Hz).

Show optional PowerShell / Registry command (advanced)Command / Path / Setting
Command / Path / Setting
Get-CimInstance -Namespace root\wmi -ClassName WmiMonitorListedSupportedSourceModes | Out-Null; dxdiag /t "$env:TEMP\dxdiag_display.txt" ; Select-String -Path "$env:TEMP\dxdiag_display.txt" -Pattern "Current Mode"

Frequently Asked Technical Questions

Why do competitive guides say V-Sync ON in NVIDIA Control Panel when using G-Sync?

With G-Sync ON and V-Sync OFF, minor frame-time spikes can still push a frame faster than your refresh window, causing tearing in the bottom 20% of the screen. Enabling Driver V-Sync + capping 3+ FPS below Hz instructs G-Sync to wait micro-fractions for scanout alignment without ever engaging classic high-latency V-Sync.

Is Uncapped 500 FPS better than G-Sync on a 240Hz or 360Hz monitor?

At 500+ FPS on a 240Hz/360Hz display, tearing lines are faint and scanout happens every 2–4 ms, giving slightly lower raw click-to-photon latency (~1–2 ms faster than a 237 FPS cap) ONLY if your GPU stays below 95% load via Reflex. If your GPU hits 99% uncapped, latency actually gets WORSE than a capped VRR setup.

Does OLED 240Hz/360Hz/480Hz still need DyAc or ULMB strobing?

OLED pixels transition almost instantaneously (~0.03 ms), eliminating LCD ghosting trails, though sample-and-hold persistence blur still scales with refresh rate. At 360Hz–480Hz OLED, motion clarity already approaches strobed 240Hz TN panels without losing VRR or brightness.

What FPS cap should I use on a 165Hz, 240Hz, or 360Hz monitor with VRR?

Use 160–162 FPS on 165Hz, 234–237 FPS on 240Hz, and 342–348 FPS on 360Hz (higher refresh monitors need a slightly wider ~4–5% margin because frame-time variance is narrower). If NVIDIA Reflex is ON with Driver V-Sync + G-Sync, you can leave the cap unset because Reflex handles it automatically.