Graphics & controls

Witcher 3 Remastered dodge input delay: patch 5.01 and comparison checks

Check the official 5.01 dodge-response fix, separate it from frame-generation latency and empty-stamina cases, and compare the same action on your installed build.

Patch 5.01 explicitly fixes delayed dodge responses and a sprint-plus-dodge case with fully depleted stamina. Update to your platform's current supported build before adding a workaround for a launch bug. The October 8 release covers PC, PS5 and Xbox Series X|S. The October 19 Switch 2 notes separately confirm the delayed-dodge fix on that platform. The Japanese version was awaiting certification in that announcement; its later release status is not verified here.

Check the build, not only the download size

Read the installed game version after the update completes. SteamDB lists the October 8 Steam 5.01 build, but a different storefront's download size does not prove a new numbered patch. Preserve a working save; do not downgrade to recreate the bug.

The Mortismal Gaming patch overview and its visible player comments discuss dodge improvements. Comments are individual results, not a latency benchmark for every controller or platform.

Make the symptom reproducible

  1. Use the same safe area, loaded character and control scheme.
  2. Press the mapped dodge action once while stationary and with stamina available.
  3. Compare the action during the situation that failed, noting sprinting and stamina state.
  4. On PC, compare keyboard and controller if both are available, with the same display settings.
  5. Record whether the action starts late, is ignored, or produces the wrong action.

Keep a dodge test separate from a roll binding or a repeated menu input. A changed animation alone is not a measured input-latency improvement. Do not deliberately overwrite your only good save with a test character.

If the entire game feels delayed

If camera movement, menu selection and combat all feel late, compare frame generation and base responsiveness. Keep resolution and the test scene unchanged when comparing one graphics setting. Higher generated FPS is not proof of lower control latency.

If a controller produces two actions instead, use the Steam double-input checklist. The 5.01 dodge fix does not certify every controller remapper or a fix for all frame-generation symptoms.

Provide a useful continuing-bug report

For a continuing failure on 5.01 or newer, preserve the save and provide platform, exact build, device, mapped action, stamina/sprint state and a short capture showing one press. Include mods and the graphics setting changed in the comparison. The patch addresses named cases; it does not prove every reported missed input has the same cause.

Sources and limits

Sources checked October 11, 2026. This is an attributed route or diagnostic checklist, not our firsthand game test. Record your exact platform and build when comparing results.