Input latency is a chain
In Kingdom Come: Deliverance II, the path from your hand to a rendered frame crosses the device driver, the operating system, the game’s polling loop, and the display. A slow link anywhere in that chain feels identical to a broken link. Fix the chain in order, not by buying a new mouse first.
The input audit
- Test the device on a known-good title. If the lag follows the device, stop here.
- Check the connection: wired first, a direct USB port rather than a hub, and no wireless receiver behind a metal case.
- Disable the game’s own smoothing, acceleration, and deadzone helpers, then retest.
- Confirm the in-game refresh rate matches the display mode Windows is actually using.
- Record one clip at 240 fps with a hardware timer if you are comparing two configurations.
A clean Kingdom Come: Deliverance II control path
Low-latency baselineThese four changes solve most reported latency complaints.
- Set the display to its native refresh rate before launching the game.
- Cap frame rate below refresh to keep the render queue short.
- Turn off in-game motion blur and camera smoothing for competitive play.
- For controllers, use a wired connection and re-test the deadzone after any firmware update.
Raw mouse input and controller detection
On CryEngine, the raw-input flag is not always exposed in the menu. When the game ignores a controller or reports the wrong device, close every virtual controller driver, unplug the extra devices, and let the game re-enumerate. A wireless headset that presents itself as a gamepad is a classic culprit.
If the game supports a config or launch path, keep the input values with the rest of your tested settings:
r_VSync=0
r_Width=2560
r_Height=1440
sys_MaxFPS=0
r_ShadersAsyncCompiling=1 Force feedback is a separate subsystem
For wheel users, force feedback quality depends on the game’s telemetry rate and the wheel’s firmware, not on the graphics preset. Verify the wheel in its own control panel first, then set the in-game rotation to match the hardware. If the wheel detects but the force feedback is dead, restart the game after the wheel software has initialised — not before.
Verify the fix
Peripheral verification for Kingdom Come: Deliverance II
0 / 5 completeThe line to keep
A stable 141 fps with a short render queue beats a fluctuating 240 fps every time. Latency is what the queue does, not what the number says.
Did this fix work on Patch 1.5.2 — combat and save fixes?
One click. No account. Your vote is stored in this browser and de-duplicated per file.
Verified against 1.5.2 — combat and save fixes. Votes are local-only telemetry.
Kingdom Come: Deliverance II: bench questions
2 answersIs this Kingdom Come: Deliverance II fix safe for my current save?
How do I know the controls & peripherals fix worked?
Controls & Peripherals
This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.
Kingdom Come: Deliverance II: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise Kingdom Come: Deliverance II on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on CryEngine.
Kingdom Come: Deliverance II: Shader Stutter, Frame Pacing & CryEngine Config Tuning
A measured stutter-hunting routine for Kingdom Come: Deliverance II: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact CryEngine settings file to edit.
Kingdom Come: Deliverance II: Safe Mod Install, Load Order & Post-Patch Conflict Recovery
Install mods on Kingdom Come: Deliverance II without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.