Why Your Game Feels Delayed
You've checked your ping. Your FPS counter says 144. But the game still feels wrong — like you're playing through a buffer. This is the signature of high input lag, and it's fixable. Here's how to diagnose it systematically.
The Feel Problem
Perceived game responsiveness is determined by the time from your physical action to a meaningful visual confirmation. Ping measures server acknowledgment. FPS measures render throughput. Neither captures the full end-to-end local latency — the part that creates the subjective 'feel' of a game.
Human perception of lag has a threshold around 30 ms for fast-twitch tasks (aiming, reacting). Below 20 ms, the game feels tight. Above 50 ms, even casual players notice the disconnect between input and action.
The Usual Suspects
V-Sync Enabled
V-Sync is the single highest-impact input lag culprit on most systems. At 60 Hz V-Sync, each frame waits for the next 16.67 ms scanout window — adding up to 16.67 ms of delay on every frame. At 144 Hz with V-Sync, the worst case is 6.94 ms. Disable V-Sync in-game and in GPU driver settings.
GPU Pre-Rendered Frame Queue
The default NVIDIA setting allows the GPU to queue 3 frames ahead of the display pipeline. This smooths out GPU workload variance but adds 2–3 frames of render latency. Set Max Pre-Rendered Frames (or Low Latency Mode) to 1 or Ultra.
CPU Power Plan
The Balanced power plan parks CPU cores during light workloads. Frame startup latency spikes occur as the CPU ramps up from a parked state. Switch to High Performance or Ultimate Performance.
Monitor in Wrong Input Mode
Many monitors have input lag reductions tied to specific display modes (PC/Game mode vs. Cinema/Movie mode). Some monitors' 'Game Mode' can reduce display processing delay by 10–30 ms. Check your OSD settings.
The V-Sync Latency Tax
Traditional V-Sync forces the GPU to wait for the display's vertical blanking interval before presenting a new frame. If your frame finished rendering at 5 ms and the next scanout is at 6.94 ms (144 Hz), the frame waits 1.94 ms. If the frame takes 7 ms to render — just over the scanout budget — it waits the full next 6.94 ms period.
NVIDIA G-Sync and AMD FreeSync eliminate this penalty within their dynamic range by making the monitor wait for the GPU, not vice versa. If you have an adaptive sync monitor, use G-Sync/FreeSync with V-Sync disabled in-game (let the display handle sync). This gives you low tearing risk without the sync-stall penalty.
Display Response Time vs Input Lag
Response time (GtG) measures how fast a pixel changes from one color to another. A 1 ms GtG monitor can still have 10 ms of input lag from its internal scaler. These are different quantities measured at different points.
High overdrive settings (in some monitors labeled 'Extreme' or 'Super Fast') push pixel transitions faster than the panel can handle, creating inverse ghosting (white halo artifacts behind fast-moving objects). This visual artifact doesn't directly cause input lag but degrades visibility of targets.
Diagnostic Flow
Step 1 — Disable V-Sync everywhere
In-game settings, NVIDIA Control Panel (or AMD Adrenalin), and any overlay applications. Run uncapped FPS and observe feel.
Step 2 — Switch power plan to High Performance
Settings → System → Power & battery → Best performance. Then relaunch the game.
Step 3 — Set GPU pre-rendered frames to 1
NVIDIA: NVCP → Manage 3D Settings → Max Pre-Rendered Frames → 1. AMD: Adrenalin → Advanced → Anti-Lag → Enabled.
Step 4 — Check monitor input mode
Enter your monitor's OSD and confirm it's in PC/Game mode, not Cinema or Movie mode.
Step 5 — Run the Responsiveness Lab
Baseline your system with our browser-based tests. Compare Mouse Smoothness and Reaction Time scores before and after changes to verify improvements.
Frequently Asked Questions
Test your setup