Input lag is the delay between a physical control action and the corresponding visible result. It is an end-to-end path, not one setting: the controller or mouse, connection, operating system, game simulation, render queue, GPU, display link, and panel can each contribute. Network delay is a different path and should be tested separately.
Describe the symptom precisely
Record the device, game, mode, scene, controller, connection type, display, resolution, refresh rate, frame rate, and when the delay began. Note whether menus, offline play, and another game show the same behavior. A delayed online character response with immediate local menu movement may point to a different problem than a cursor that feels slow everywhere.
NVIDIA's Reflex SDK documentation breaks measured latency into pipeline stages that include input, simulation, render submission, driver, render queue, and GPU rendering. Vendor tools apply only to supported hardware and games, but the staged model is useful: measure the whole response first, then narrow the stage instead of changing unrelated settings.
Establish a repeatable baseline
Choose one action with a clear visual response and repeat it under the same conditions. Use a game's built-in latency metric when available and understand what portion it measures. A phone recording can help compare large differences, but it is not a calibrated measurement unless capture frame rate, timing, and review method are controlled. Avoid quoting a precise millisecond result from an informal test.
Test a wired controller or mouse if supported, then another known-good input device. Remove unnecessary hubs, charge wireless devices, and check for firmware updates from the manufacturer. Keep the game and display settings fixed while testing the input path. Then return to the original device to confirm the change follows it.
Check frame production and presentation
Low or unstable frame rate can increase the time before an input appears in a completed frame. Record frame rate and frame pacing, reduce one demanding setting, and compare the same scene. Do not assume the fastest-looking preset is automatically the lowest-latency configuration on every system.
Microsoft's windowed-game optimization guide says the supported Windows 11 feature moves compatible DirectX 10 and 11 windowed games to a newer presentation model, reducing frame latency and enabling features such as variable refresh rate on supported displays. Test platform features per game and keep a rollback note because compatibility varies.
Check whether the display is in its intended low-latency or game mode, and disable image-processing features only according to the display manual. Confirm the active refresh rate and cable path. If a television passes through a receiver or capture device, test a direct connection to isolate that stage.
Separate local and online delay
Repeat the action in an offline or local training mode. If local response is normal but online play is delayed, record network latency, packet loss, server region, and service status without calling the symptom input lag. If both are delayed, continue isolating local stages.
A practical diagnosis ends with evidence: one controlled change produced a repeatable difference and returning to the old configuration restored the symptom. Save the working settings, driver version, display mode, and test conditions so a future update can be compared rather than guessed at.
Sources
- NVIDIA Reflex — NVIDIA Developer
- Optimizations for windowed games in Windows 11 — Microsoft Support