Start with one repeatable guard or parry attempt in a safe, preferably offline encounter. If every action appears late, investigate the input-to-display path; if one press disappears, investigate the controller, connection, or bindings; if the game sees the press but the defense fails, learn that game’s timing rule. Work through display settings, frame presentation, input hardware, and game-specific mechanics in that order before buying equipment. Local input lag can occur entirely offline and is separate from online network delay.
What kind of “input lag” are you actually seeing?
Missed parries have several different causes that feel similar. Separating them prevents you from changing graphics settings when the real problem is a worn button, or buying a monitor when the game requires a different defensive input.
Every action reacts late
Open a menu, move through inventory, or perform a simple attack in the same offline encounter. If those actions consistently appear behind your press, examine the display, frame pacing, synchronization, and controller path.
One press sometimes disappears
If movement and menus work but guard or parry presses vanish, suspect the device, cable or wireless link, USB port, power state, or a mapping layer. A binding conflict can also send a different action than the one shown on screen.
The game reacts, but the deflect fails
A guard animation or blocked hit shows that an input arrived; a failed deflect can therefore be a timing or rules issue. Each game defines its own press, hold, release, buffer, and animation rules. Do not assume a window from one action game applies to another.
How do I establish a repeatable baseline?
Use the same attack cue and the same defensive input for every comparison. Change one variable at a time, then repeat the encounter under matching conditions.
- Choose an offline area with a predictable enemy attack. Online play can add network delay, so it is not a clean baseline for local input.
- Record three observations: whether simple actions respond, whether guard appears, and whether the hit is blocked or deflected.
- Repeat the attempt several times without changing your position, camera distance, frame-rate limit, or control layout.
- Make one change, such as enabling TV Game Mode or switching V-Sync, and repeat the same sequence.
- Keep a short note of the setting, average frame rate, visible tearing, and whether the defensive result changed. This is a comparison log, not proof that one setting will improve every game.
Offline consistency separates local timing concerns from online-only symptoms, but it does not identify the exact failing component by itself.
Which display settings should I change first?
Free display checks come before a monitor purchase. Confirm that the operating system and the game are using the display’s intended refresh rate, and remove processing that delays a television’s picture.
Verify the selected refresh rate
In Windows, open Settings → System → Display → Advanced display and check the active refresh rate. Select the highest rate that your display and connection genuinely support, then confirm the game has not selected a separate lower mode. A higher refresh rate shortens the display refresh interval, but it cannot erase controller, rendering, or game-rule delays.
Enable a television’s Game Mode
Televisions often apply motion interpolation, noise reduction, sharpening, or other processing intended for video playback. Game Mode normally bypasses some of that work. Menu names differ by manufacturer, so look under picture presets or external-input settings. Disable processing only for the input used by the PC; other sources can retain their normal picture mode.
Prefer a direct display connection
If the PC is using a wireless display path, compare a direct wired connection supported by the computer and monitor or television. Wireless display adds another variable and is unsuitable for diagnosing a tight defensive window.
Do not confuse pixel response time with input lag
A panel’s advertised gray-to-gray or pixel response time describes how quickly a pixel changes. Total input lag also includes signal processing, scan-out, synchronization, rendering, and the controller path. Use independently measured display input-latency data when comparing hardware; a response-time advertisement is not a complete latency measurement.
Should V-Sync be off, or should I use VRR?
There is no universal V-Sync recipe. The choice is a trade-off among response, tearing, frame pacing, hardware support, and the game’s implementation.
Use V-Sync off as a diagnostic
Turn in-game V-Sync off and repeat the baseline. If the controls feel more immediate but horizontal tearing appears, you have identified a presentation trade-off rather than a complete fix. Record both observations; a setting that feels faster but produces distracting tearing may not be practical for long sessions.
Compare supported VRR and a sensible frame cap
Variable-refresh technologies, called Adaptive Sync or VRR depending on the display and GPU, can align refresh with delivered frames within their supported range. Test VRR with a frame cap that keeps frame delivery stable and inside that range. The best cap depends on the display’s refresh limit and the game’s ability to sustain the target; do not copy a number from another system.
Understand the V-Sync/VRR/latency trade-off
NVIDIA documents combinations that reduce tearing while retaining low latency on compatible hardware, while completely uncapped rendering can trade tearing for lower latency. Steam’s Counter-Strike 2 support specifically recommends a V-Sync, G-Sync, and Reflex combination on compatible systems. That recommendation is game- and hardware-specific, not a rule for every action game.
Compare exclusive fullscreen and borderless
If the game offers both modes, test them under the same frame cap and synchronization settings. Windows presentation behavior has changed across versions, so an older vendor recommendation does not guarantee that exclusive fullscreen is faster on every current system.
How can frame rate and frame pacing affect a parry?
More frames can make a visual cue arrive sooner and more consistently, but an unstable frame stream can make timing feel irregular. Lower graphics demand when frame time spikes coincide with missed defenses.
Use the game’s own frame-time information
Watch for uneven frame times, stutter, or drops during the attack cue. Reduce expensive options such as shadows, volumetric effects, or resolution scaling one at a time. The goal is a stable delivery pattern, not a decorative maximum setting.
Interpret illustrative frame-rate targets correctly
An Intel support example compares 59 frames per second on a 60 Hz display with trying 120 or more frames per second. Those figures are options to compare on a particular system, not a promise of a fixed latency reduction or more successful parries. Keep the result that feels more responsive while remaining stable.
When should I test NVIDIA Reflex or driver low-latency mode?
If the game and GPU support NVIDIA Reflex, test the game’s Reflex option before relying on a driver override. NVIDIA presents driver Low Latency Mode as a fallback when Reflex is unavailable; stacking both is not established as an automatic improvement.
- Open the game’s graphics or latency settings and enable Reflex if the option is present.
- Restart or reload the game if it requests that, then repeat the same offline encounter.
- Compare frame pacing and responsiveness rather than assuming the label guarantees a result.
- If Reflex is unavailable, test the driver’s Low Latency Mode as a separate configuration, not an additive layer.
These settings influence the rendering queue. They cannot repair a failing switch, a conflicting binding, or a parry rule that requires a different input.
How do I tell whether my controller or keyboard is dropping inputs?
Use a known-good device and compare paths under identical conditions. A wired cable is useful for diagnosis, but it is not automatically faster than every modern wireless connection.
Compare another device
Connect a controller or keyboard known to work reliably. Use the same binding and the same encounter. If the second device makes the missing presses disappear, inspect the original device’s button, battery, firmware, or physical connection.
Test wired and wireless separately
For a controller that supports both modes, compare a working USB data cable with wireless. Confirm that the cable carries data rather than power only, and that the controller is actually operating in wired mode. Modern wireless implementations can be responsive; the comparison is diagnostic, not proof that wired always wins.
Try another USB port
Move the device to another port when response changes by port, connections drop, or presses arrive irregularly. Steam documents USB scheduling and contention as possible explanations for intermittent behavior. Disconnect unnecessary high-bandwidth USB devices during the comparison.
Check bindings and Steam Input
Open the game’s controller or keyboard binding screen and verify that guard and parry are assigned to the intended button. Then inspect Steam’s per-game controller layout. Steam Input can emulate gamepad input, and Activision has noted possible Steam/game configuration conflicts for Sekiro. That does not establish that Steam Input inherently adds a specific number of milliseconds; treat it as a configuration variable to compare.
Check power and connection reliability
Recharge a wireless controller, replace a failing battery, and watch for disconnect notifications. A single dropped packet or reconnect can look like a missed parry even when the display and frame rate are fine.
How do game-specific parry rules change the diagnosis?
Learn the named game’s defensive rule only after the hardware and presentation path is stable. “Parry” can mean a timed press, a held guard, a release, a directional input, or a move with its own startup animation.
Sekiro as a concrete example
FromSoftware’s web manual distinguishes holding guard from a timed deflect. It describes pressing the guard button “the moment before a blow lands” to deflect, while holding the control guards. This is an example of one game’s rule, not a universal parry-window measurement for PC action games.
Use the attack cue, not a guessed millisecond value
Practice against the same wind-up and impact animation. If a held guard consistently blocks but does not produce a deflect, the press timing or the game’s required action is more likely than a missing input. Avoid inventing active-frame counts, buffering rules, or animation-cancel behavior when the game has not been identified.
Check whether the game buffers inputs
Some games accept an input during recovery or a preceding animation; others require the character to be actionable. Look for the game’s manual or official documentation before changing your timing. A press that is visible in an input overlay can still be ignored by the game’s state machine.
What can latency tools measure?
Use tools to narrow the rendering problem, not to claim a complete button-to-photon result. NVIDIA FrameView 1.7 can report average FPS, 1% low FPS, and PC Latency where supported.
Understand the PC Latency boundary
FrameView’s PC Latency focuses on the PC portion of the path. It excludes controller delay and display delay. A lower PC Latency number therefore does not prove that the entire controller-to-screen chain improved, and it cannot establish a higher parry success rate.
Record before-and-after observations honestly
Save the same scene’s frame-rate and frame-time information before and after one change. Report the tool’s metric with its scope and conditions. Do not describe an unperformed benchmark as a measured improvement.
When is buying a monitor or controller justified?
Purchase hardware only after free settings and substitution tests identify a remaining constraint.
Choose a display for a confirmed display limitation
A suitable gaming monitor with variable refresh rate may help when the existing display has high independently measured input latency, lacks the required refresh mode, or cannot maintain the desired synchronization range. Compare measured input latency, VRR range, connector compatibility, and the refresh rate your PC can sustain. A new panel cannot correct a wrong binding or a game-specific timing rule.
Choose a controller for reliability, not a guaranteed millisecond claim
A PC-compatible wired gamepad is a reasonable known-good comparison when the current controller drops presses or disconnects. Verify operating-system and game compatibility, button condition, and whether the game uses a mapping layer. No universal wired-controller advantage has been established for every modern device.
Use the right cable for diagnosis
A controller-compatible USB data cable can isolate wireless or power problems, provided the connector and data mode match the controller. It is not a guaranteed latency reduction by itself.
What common fixes fail, and why?
- Buying a monitor based only on pixel response time: this omits the display’s actual signal-processing and input-latency behavior.
- Copying one V-Sync setting everywhere: synchronization support, frame rate, VRR range, and tearing tolerance differ by game and system.
- Enabling every low-latency option at once: you lose a clean comparison, and Reflex plus a driver override is not proven to stack beneficially.
- Assuming wireless is the cause: modern wireless can be responsive; intermittent failures may instead come from power, interference, mapping, or USB contention.
- Practicing a guessed universal parry window: each game can require a different press, hold, release, direction, or animation state.
- Treating a lower PC Latency metric as a complete victory: controller and display delay remain outside that measurement.
- Changing several settings between attempts: without a repeatable baseline, you cannot tell which change affected the symptom.
How should I work through the diagnosis?
Use this order to avoid spending money before identifying the failure:
- Reproduce the same offline guard or parry attempt and classify the symptom.
- Verify Windows and in-game refresh rate, enable TV Game Mode if applicable, and remove unnecessary display processing.
- Compare V-Sync off with supported VRR and a stable frame cap; note tearing and frame pacing.
- Test game Reflex when supported, or driver Low Latency Mode only when Reflex is unavailable.
- Lower graphics settings if frame delivery is unstable.
- Compare a known-good controller or keyboard, another USB port, and supported wired and wireless modes.
- Inspect game bindings and Steam Input configuration for conflicts.
- Read the specific game’s manual or official guidance and practice the documented defensive action.
- Use FrameView or another supported overlay to record FPS, frame time, and PC Latency with their limits stated.
- Consider a display or controller purchase only when the comparison identifies a hardware constraint.
This sequence cannot guarantee a successful parry in every encounter. It does make the cause more specific: presentation delay, unstable rendering, dropped input, configuration conflict, or a game rule that differs from your assumption.
Frequently Asked Questions
Can a high-ping connection cause parries to miss in an offline game?
No. An offline encounter removes network transit from the equation, although local input, rendering, and display delay can still exist. If the same attempt fails offline and online, investigate the local path first; if it fails only online, network conditions become a separate line of inquiry.
Does a 1,000 Hz polling rate guarantee a faster parry?
No. NVIDIA’s 2020-era optimization guide cites approximately 3 ms of additional average system latency at 125 Hz compared with 1,000 Hz for a mouse-focused scenario. That figure is not an independently verified gamepad result and does not account for display or game timing.
Why does my input overlay show the button, but the character still gets hit?
The game may receive the press while the character is in recovery, stunned, out of range, or using a guard state that blocks without deflecting. Check the game’s action-state and buffering rules rather than assuming the button signal was lost.
Is borderless fullscreen always slower than exclusive fullscreen?
No universal ordering is established for current Windows systems. The result depends on the game’s presentation path, synchronization settings, driver behavior, and frame pacing, so compare both modes under the same conditions.