When your crosshair lands where your hand stopped moving a quarter-second ago, or your character stumbles through a doorframe that should have been clear, you are almost certainly dealing with input lag rather than low frame rate. These two problems look identical in a gameplay clip but demand completely different fixes. A 144 FPS render running on a 144 Hz panel with V-Sync forced on can feel as sluggish as a 40 FPS slideshow. The pipeline from your mouse microswitch to the photon leaving your monitor involves at least six stages—peripheral debounce, USB polling, CPU submission, GPU queue, panel scanout, and pixel response time—and a bottleneck at any one of them produces the same “floaty” sensation in your hands.
- Likely Causes
- Fix 1: Disable V-Sync Everywhere and Replace with In-Game Frame Cap
- Fix 2: Enable NVIDIA Reflex or AMD Anti-Lag
- Fix 3: Maximize USB Polling Rate
- Fix 4: Force Exclusive Fullscreen or Bypass DWM
- Fix 5: Reduce GPU Frame Queue Depth via Driver Settings
- Fix 6: Disable Windows Game Mode and Overlays
- Fix 7: Calibrate Display Response Time Overdrive
- If Nothing Works
- FAQ
In 2026 the landscape is more fragmented than ever. Unreal Engine 5 titles lean on Nanite and Lumen for visual fidelity, which can silently inflate GPU frame times. Competitive shooters like Counter-Strike 2 and Valorant now ship with built-in Reflex or Anti-Lag toggles that most players never enable. Meanwhile, Windows 11’s compositor and the legacy flip-model presentation path interact in ways that add two or three extra frames of latency depending on whether you are running exclusive fullscreen, borderless, or a driver-forced fullscreen override. This article walks through the checks and fixes that actually move the needle, ordered from least invasive to most invasive.
Likely Causes
| Cause | How to Confirm | Fix Difficulty |
|---|---|---|
| V-Sync active (driver or in-game) | Open NVIDIA Control Panel or AMD Adrenalin; check Vertical Sync. In-game, type cl_vsync_mode 0 in Counter-Strike 2 console or inspect Engine.ini under [/Script/Engine.RendererSettings]. |
Easy |
| Frame limiter above or at refresh rate with no buffer control | Use MSI Afterburner OSD: if GPU frame time varies by more than 2 ms between consecutive frames while FPS is stable, the frame queue is back-filling. | Easy |
| USB polling rate below 1000 Hz | Open Device Manager, expand Human Interface Devices, right-click your mouse, check Properties > Details > Device instance path. A “PollRate” value of 125 or 500 confirms the issue. | Easy |
| Hardware-Accelerated GPU Scheduling disabled or conflicting with driver | Settings > System > Display > Graphics > Change default graphics settings. If the toggle is off, your CPU-GPU handshake adds a copy operation. | Moderate |
| NVIDIA Reflex / AMD Anti-Lag not engaged | Check in-game video settings. In Fortnite, the option lives under Video Settings > Advanced > NVIDIA Reflex Low Latency. In Apex Legends, it is under Video > Anti-Aliasing < AMD Radeon Anti-Lag. | Easy |
| Display pixel response time masking as input lag | Use the UFO Test on your panel: if ghosting or overshoot is visible on the moving target, perceived lag is actually overdrive/undershoot, not pipeline latency. | Moderate |
| Windows Game Mode or overlay injecting compositor overhead | Run dxdiag, check Display tab for “Feature Levels 12_2” and confirm DWM is not in legacy composition mode. Close Discord/Steam overlay and retest. |
Easy |
Fix 1: Disable V-Sync Everywhere and Replace with In-Game Frame Cap
How to check
Launch your game, open the developer console (backtick key in Source-engine titles, tilde in Unreal titles), and run cl_showfps 1 or stat unit. If the “Swap” column shows two frames consistently behind “Game” and “Draw,” V-Sync is queueing frames. Also check NVIDIA Profile Inspector: look at SyncToRefreshInterval and SyncToRefreshIntervalBeforeAppStarts.
What to do
Set Vertical Sync to “Off” in both your game’s video menu and your driver control panel. Cap FPS to your monitor’s refresh rate minus two to three frames (141 for 144 Hz, 237 for 240 Hz) using the game’s built-in limiter or RivaTuner Statistics Server frame limiter. This keeps the GPU queue at depth one without introducing tearing.
How to undo it
Return each setting to its original value. No files are modified; all changes are reversible through the same menus.
Fix 2: Enable NVIDIA Reflex or AMD Anti-Lag
How to check
In supported titles, open Video Settings and search for “Reflex” or “Anti-Lag.” If the option is absent, the game does not expose it—check the developer patch notes or the game’s config.ini (found in %LOCALAPPDATA%\\[GameName]\\Saved\\Config\\Windows\\ for Unreal titles) for a commented-out entry like ;[/Script/Engine.RendererSettings].
What to do
Set Reflex to “On + Boost” (the boost variant keeps GPU clocks elevated, reducing clock ramp latency on the first few frames after idle). For AMD, enable “Radeon Anti-Lag” in Adrenalin under Graphics > Global or per-game profile. In Counter-Strike 2, the launch option -novid -fullscreen combined with Reflex (enabled by default since the 2023 update) is the standard baseline.
How to undo it
Set the option back to “Off” or “Disabled” in the same menu.
Fix 3: Maximize USB Polling Rate
How to check
Use a tool such as the official Logitech G HUB or Razer Synapse software to read your mouse’s current polling rate. Alternatively, download MouseRateChecker (a standalone utility) and observe the Hz value during rapid movement. Many office-grade or wireless mice default to 125 Hz.
What to do
Set polling to 1000 Hz if your mouse supports it. For 4K Hz capable devices (Razer Viper V3 Pro, Logitech G Pro X Superlight 2 with the optional 4000 Hz firmware toggle in G HUB), enable it only if your CPU has headroom—4K polling adds measurable CPU load in Unreal Engine 5 titles like Fortnite and can paradoxically increase input-to-render latency on a weak processor. Use a wired connection where possible; 2.4 GHz wireless dongles at 1000 Hz add roughly 0.5 ms of radio latency.
How to undo it
Return the polling rate to its previous value in the mouse software or reconnect your original USB cable.
Fix 4: Force Exclusive Fullscreen or Bypass DWM
How to check
In borderless windowed mode, the Desktop Window Manager composes your game’s output before sending it to the display, adding one to two frames. Confirm by comparing frametime in CapFrameX between borderless and exclusive fullscreen on the same settings.
What to do
Launch the game in exclusive fullscreen. For Steam titles, add -fullscreen or -vulkan -fullscreen in Properties > Launch Options. For games that stubbornly run borderless regardless (some UE5 shipping builds), check the game’s ini file for FullscreenMode=2 (which means borderless) and change it to 0 (exclusive) or 1 (windowed). On NVIDIA, enable Flip-mode present via the driver to reduce DWM overhead even in windowed apps.
How to undo it
Delete the launch options and revert the ini value.
Fix 5: Reduce GPU Frame Queue Depth via Driver Settings
How to check
Open NVIDIA Profile Inspector (the legacy low-level override tool) and look at Maximum pre-rendered frames. A value of “Use the 3D application setting” often resolves to 3 on older drivers. In AMD Adrenalin, the equivalent is Wait for Vertical Refresh combined with Anti-Lag internal queue behavior.
What to do
Set Maximum pre-rendered frames to 1. This caps the CPU-ahead-of-GPU buffer at a single frame, meaning your input is reflected in the next render rather than the one after that. If you experience micro-stutter after this change, your CPU cannot keep the GPU fed and you should revert.
How to undo it
Reset the profile to default in NVIDIA Profile Inspector or delete the custom profile.
Fix 6: Disable Windows Game Mode and Overlays
How to check
Game Mode, Xbox Game Bar, Steam Overlay, Discord Overlay, and GeForce Experience overlay each hook the present chain. Open Task Manager > Details while the game is running; look for GameBar.exe, Discord.exe with an active overlay, or GFExperience.exe consuming CPU spikes during gameplay.
What to do
Turn off Game Mode in Settings > Gaming > Game Mode. Disable Xbox Game Bar under Settings > Gaming > Xbox Game Bar. In Steam, right-click the game > Properties > General > uncheck “Enable the Steam Overlay.” In Discord, Settings > Game Overlay > toggle off. Test after each change to isolate the culprit.
How to undo it
Re-enable each setting individually.
Fix 7: Calibrate Display Response Time Overdrive
How to check
If fixes 1 through 6 are already applied and the game still feels “mushy,” your monitor’s overdrive level may be causing inverse ghosting or slow pixel transitions. Use the Blur Busters Test UFO (run locally from the Blur Busters site) and observe the moving target at each overdrive setting.
What to do
Set your monitor’s overdrive to “Normal” or “Medium.” High settings create corona artifacts that the brain reads as motion smear, which is often mistaken for input lag. Some 2026 QD-OLED panels offer per-color overdrive; leave it at the default calibration profile unless you are willing to benchmark pixel response with a photodiode.
How to undo it
Restore your previous overdrive setting via the monitor OSD menu.
If Nothing Works
Run a controlled A/B test: capture 30 seconds of gameplay with a visible system clock (use OBS Studio with a time source filtered to 1000 Hz) and measure the distance between your hand stopping (visible on a second camera or by watching the cursor) and the in-game crosshair settling. If the gap exceeds 30 ms consistently, the remaining suspects are a faulty USB hub (connect the mouse directly to a rear I/O port on the motherboard), a failing GPU that is clock-throttling (monitor with hwinfo64—look for “Perf Capability Events” or “Slowdown” flags), or a monitor that does not actually achieve its advertised response time (check TFTCentral or RTINGS measurements for your specific panel batch). In rare cases, a BIOS-level USB controller misconfiguration (xHCI hand-off disabled, or USB power management set to “Aggressive”) introduces 5-10 ms of random jitter; update your motherboard BIOS and set USB power to “Normal.”
FAQ
Does a higher refresh rate reduce input lag even if I cannot hit that frame rate?
Yes, but only partially. A 240 Hz panel updates the displayed image every 4.2 ms versus 8.3 ms on 120 Hz, so the average wait between a completed frame and its scanout halves. However, if your GPU only delivers 120 FPS, you still experience the 4.2 ms benefit because the frame queue is empty and each rendered frame is displayed at the next scanout boundary. The gains diminish beyond 360 Hz unless your hardware sustains frame rates above 250.
Why does my game feel faster in windowed mode than fullscreen on Windows 11?
On some driver versions, the flip-model presentation path is not used in exclusive fullscreen, forcing a copy through the DWM swap chain. In borderless windowed, the compositor may actually take a more direct path if Hardware-Accelerated GPU Scheduling is enabled. Test both modes with CapFrameX and compare “GPU busy time” and “present latency” columns rather than trusting feel alone.
Will an SSD reduce input lag compared to a hard drive?
No. Input lag refers to the per-frame pipeline from peripheral to display. An SSD affects texture streaming and level loading, not the latency of individual input events being processed and rendered. If your game stutters because textures cannot load fast enough, that is a frame-time issue, not an input-lag issue. Fix it by reducing texture settings or upgrading storage, but do not confuse the two.
Does NVIDIA Reflex help if my GPU is already at 99% utilization?
Especially yes. Reflex’s primary value is reducing the CPU-to-GPU frame queue when the GPU is the bottleneck. At 99% utilization, the traditional pipeline may hold three or four frames in the render queue while the GPU works through them, meaning your input is reflected in a frame rendered three frames ago. Reflex collapses that queue to one frame, which can shave 15-25 ms of perceived latency on heavy titles like Cyberpunk 2077 with path tracing enabled.
