vsync input lag and framepacing conflict simulator
The Capsule Tools vsync input lag and framepacing conflict simulator is a free, browser-based dashboard that visually demonstrates what mismatched refresh rates, framerates, and VSync modes actually do to motion on your screen. Pick a monitor refresh rate, drag the framerate, switch between Off / Double / Triple VSync, toggle VRR, and watch tearing, stutter, or smooth motion appear in real time — alongside the effective FPS and input lag those settings produce.
It's built for the moment you've already spent two hours reading conflicting Reddit threads and want a single place to see, with your own eyes, why your $2000 PC still feels like a slideshow. No download, no install, no game database — just cause and effect.
Why does my 144Hz monitor feel choppy like 60Hz
The single most common reason a high-refresh-rate monitor feels nothing like its spec: the game's framerate doesn't reach the monitor's refresh rate, and double-buffered VSync is dropping the displayed output to an integer divisor. A game running at 90 FPS on a 144 Hz panel with double-buffered VSync isn't showing 90 Hz of motion — it's showing 72 Hz, because that's the next divisor under 144 the buffer can sustain.
The same logic produces the most-quoted symptom in the community: "game ended up running at basically double-speed because everything was connected to that 30fps". When the engine is locked to whatever cadence VSync hands back, every game-side timer drifts. The simulator lets you play this back at any Hz you want.
Variable Refresh Rate (G-Sync, FreeSync) avoids the entire problem by letting the monitor refresh whenever the GPU finishes a frame, up to its maximum Hz. The toggle on this tool shows that effect instantly: stutter and tearing both disappear at any framerate below the cap.
How the simulator works
The simulator computes two things from your inputs and paints them to a single canvas:
-
Effective output framerate. Off → equals your input FPS. Double-buffered → drops to
the next integer divisor of Hz when FPS can't sustain Hz (60 → 30 → 20 → 15). Triple-buffered → clamps
to
min(FPS, Hz)with no halving cliff. VRR →min(FPS, Hz)regardless of VSync. -
Input lag.
(1000 / effectiveFPS) × bufferDepth. Off = 1 buffer, Double = 2, Triple = 3, VRR = 1. This is why turning VSync on can feel like swimming through molasses on a controller.
The visual is intentionally minimal — a single bar moving across a striped background — because anything richer would risk the tool itself stuttering on low-end devices, which would defeat the whole point. Tearing is rendered as a horizontal seam where the top and bottom halves of the frame are sampled from different game frames; stutter is rendered as the bar holding position for several refreshes before jumping; smooth motion is even pixel-per-refresh.
How to use the VSync Conflict Simulator
The fastest way to make sense of the tool is to start with a known-bad combination, then fix it.
Reproduce the most common complaint
Set the monitor to 144 Hz, framerate to 90 FPS, VSync to Double, VRR off. Watch the bar — the motion is choppy, telemetry shows effective FPS at 72, and input lag spikes. That's a real-world scenario where someone's brand-new 144 Hz monitor feels worse than the 60 Hz it replaced.
Stop VSync from dropping FPS to 30 randomly
Lower the framerate to 55 FPS with VSync still on Double on a 60 Hz monitor. Effective FPS jumps to 30. This is the answer to "stop vsync from dropping fps to 30 randomly" — it isn't random; it's the divisor cliff. Switch VSync to Triple and effective FPS becomes 55 again, smoother but with more buffer lag. Switch to Off and tearing returns.
Compare a frame cap to VSync
The cleanest fix for tearing without VSync's input lag is capping the in-game framerate just below the monitor's Hz. Try vsync=Off, fps=58, hz=60: the seam disappears, lag is minimal, effective FPS is honest. This is the simulator's case for "vsync vs capping frame rate for engine stability".
Watch VRR fix everything
With any FPS below the monitor's Hz, toggle Variable refresh rate on. The bar immediately moves smoothly at the actual rendered framerate, with only one frame of buffer lag. This is what G-Sync and FreeSync are doing in real hardware: aligning each refresh to a real game frame.
A high-refresh monitor is a promise. VSync, frame caps, and VRR are how you actually keep it.
Frequently asked questions
stop vsync from dropping fps to 30 randomly
Double-buffered VSync only outputs at integer divisors of your refresh rate. The moment your game can't sustain a full 60 FPS on a 60 Hz monitor, the next available output is 30 — there's no 45 in between. Set VSync to Off and cap your in-game framerate just under your monitor's Hz (e.g. 58 on 60 Hz), or enable G-Sync/FreeSync. Either avoids the half-rate cliff entirely. Toggle the simulator to vsync=Double, fps=55, hz=60 to watch the drop to 30 happen live.
remove input lag from vsync on 60hz monitor
VSync input lag comes from buffered frames waiting in queue: roughly (1000 / FPS) × buffer
depth milliseconds. Double-buffered = 2 frames of lag, triple-buffered = 3. To remove input lag
from VSync on a 60 Hz monitor, either turn VSync off and cap the framerate one or two below 60 (which
keeps the GPU from over-rendering and producing tearing), or use a Variable Refresh Rate display so the
monitor matches the GPU — same visual smoothness, single buffer, minimal lag.
why does my 144hz monitor feel choppy like 60hz
The most common cause: your game can't actually render 144 frames per second, and double-buffered VSync is locking output to a divisor of 144 — 72, 48, or 36 — instead of letting it float. A 144 Hz monitor only feels like 144 Hz when the framerate sustains above 144. If your GPU produces 90 FPS with VSync on, you may be watching 72 Hz of motion. Disable VSync and uncap, or enable VRR. Run the simulator at hz=144, fps=90, vsync=Double to see the lock-down for yourself.
fix 144hz main and 60hz secondary stuttering issues
Dual-monitor stutter happens because the GPU is timing presents against two refresh cycles that never align. Windows usually defaults the desktop compositor to the primary monitor's refresh rate, so games on a 144 Hz primary still get pacing interference from a 60 Hz secondary holding a video or browser. Fix: enable G-Sync/FreeSync on the primary, run any second-monitor video in a borderless window rather than fullscreen, and avoid background applications doing heavy GPU work on the 60 Hz panel. The simulator's VRR toggle demonstrates how a variable refresh rate eliminates the underlying pacing conflict.
how to eliminate microstutter on dual monitor setup
Microstutter on dual monitor setups is almost always frame pacing irregularity — the GPU presents frames at intervals that aren't quite uniform, and your eye picks up the variance even when the average framerate looks fine. The fastest fix is enabling VRR (G-Sync or FreeSync) on the gaming display, which lets each frame ship the moment it's ready instead of waiting for the next refresh slot. Toggle vrr=on in the simulator with fps=90, hz=144 — the bar moves perfectly evenly. Toggle it off and the stutter pattern reappears.
vsync vs capping frame rate for engine stability
Capping the framerate slightly below your refresh rate (e.g. 58 fps on a 60 Hz monitor) is almost always preferable to enabling VSync for engine stability. A frame cap keeps the GPU from over-rendering, which avoids tearing without the buffer-queue input lag VSync introduces. Some game engines also tie physics or input timing to the render loop, and a stable cap produces more predictable behavior than a VSync target that drops to half-rate the moment performance dips. Use the simulator: vsync=Off, fps=58, hz=60 looks essentially identical to vsync=Double — without the lag.
does 75hz make a noticeable difference over 60hz
Yes — 75 Hz reduces the time between refreshes by 25% (16.7ms → 13.3ms), which is large enough to noticeably reduce motion blur and improve cursor tracking, especially on desktop scrolling and slower-paced games. The jump isn't as dramatic as 60→144, but it's real. Set the simulator to vsync=Off, fps=75, hz=75 and compare against the same fps with hz=60: motion is visibly smoother at 75 because each refresh sample is closer to the true render time.
Simulate tearing and stutter free — no install
Capsule Tools' VSync simulator is free, runs entirely in your browser, and saves nothing. Open it, change a slider, watch the canvas — that's the whole loop.
Open the simulator →