Skip to content
PBZWIKI

Does Frame Generation Make Parries Feel Late?

Frame generation adds displayed frames, not inputs. The latency comes from your base frame rate, not from the bigger number.

Updated 2026-11-01·
#PC#performance#controls

Pick from this table

Read your base frame rate first — the frame rate with generation off — then decide whether to enable it and at what multiplier:

  • Base below 60: leave it off. Lower settings or the upscaling mode and get the base up; generation will not fix input response
  • Base 60 to 90: 2x. Noticeably smoother, with a limited cost to feel
  • Base above 90: 3x, and try 4x only if you have headroom to spare
  • Hard boss attempts: turn it off and take the most direct input response

The reasoning follows below, but that table is the whole answer.

How to read your base frame rate

Turn generation off and look at the frame rate in the scene that actually stutters for you — not standing still in a town, but mid-fight with effects on screen.

That number is what decides how the game feels. With generation on, the counter shows delivered frames; it can multiply several times over without saying anything about how direct your input is.

Why parries break first

Frame generation inserts generated frames between two genuinely rendered ones. It raises how often the screen refreshes; it does not raise how often the game reads your input — the moment you press attack, the game still waits for the next real frame.

A parry depends on the order of press and judgement. Generated frames carry no new input sample, so the blade appears to reach you while the judgement still waits for the next real frame. The result feels like a dropped input or a half-beat delay.

Your hands are not late; the chain got longer. The lower the base frame rate, the longer it gets — at 6x, five of every six frames you see are generated.

Keep Reflex on, but it is tied to generation

The feature that actually shortens input latency is the low-latency mode (NVIDIA Reflex), and it is a separate thing from frame generation.

The catch: Reflex cannot be enabled independently of DLSS Frame Generation, and switching it on introduces frame-time instability of its own. Wanting lower latency therefore often means taking frame generation with it — the trade-off is not fully free.

Enable it when you can. It claws back some of the input path, which is still better than pure interpolation.

What 4x and above adds

In testing, an RTX 5060 8GB at 4K, maximum settings, ray tracing off, DLSS Balanced with 6x generation went from under 60 frames to 174, with latency held under 60 ms.

The same test found that at 4x and above, texture-dense scenes show noticeable edge aliasing and noise. So 2x or 3x is the steadier range, especially if you tend to watch cloth and distant detail.

Those figures come from public test environments; your machine will differ.

A three-step self test

  • Pick an enemy with a fixed attack pattern, or a training area, and use the same combo
  • Run five rounds each with generation off, at 2x and at 4x, recording only the press-to-swing delay
  • Choose the setting where you parry consistently, not the one with the highest counter

Related entries

Linked automatically from mentions and tags