What the Official Notes Cover
Two patches adjusted input, and both are described as adjustments rather than complete fixes.
Improved
Controller dead zones
Adjusted in Hotfix 1.0.2 on PC and adjusted again in Hotfix 1.0.4. An adjustment changes behaviour; it does not promise every drift or dead-zone complaint is gone.
Improved
Sprint input while changing direction
Hotfix 1.0.4 fixed input issues while sprinting. If sprint still stops, your case is outside what the note describes.
Still reported
PS5 button mapping
Listed in the launch known issues and not resolved by a patch note. Reported by players after 1.0.4.
Official Checks
OfficialThese apply to every controller symptom, and they must be done in this order.
Confirm your game version first
Dead zones and sprint input changed in Hotfix 1.0.2 and again in 1.0.4. A report from before those patches describes a different build.
Update the game
Then retest the exact same movement before changing any in-game setting, so the patch result is not confused with a setting change.
Change the in-game dead zone only if it is exposed
Use the game’s own setting rather than a third-party tool. An external remapper changes the input the game receives, which makes any later comparison meaningless.
Test with a cable
Wireless and cable are different input paths. Testing both separates a connection problem from a mapping problem.
Neither input note claims to fix every controller problem, so “still broken after updating” is an open case rather than a contradiction.
Match Your Symptom
OfficialEach symptom has its own first step. Start with the one that matches what you feel in game.
Sprint keeps stopping
Input while sprinting was addressed in Hotfix 1.0.4. Update, then test sprint in a straight line before testing direction changes.
The camera drifts on its own
Dead zone. Adjusted twice, on PC in 1.0.2 and again in 1.0.4. Check your version and retest before treating it as hardware failure.
PS5 button prompts are wrong or missing
Mapping. Acknowledged in the launch known issues and not covered by a patch note, so a workaround is the realistic option for now.
Community-Reported Workarounds
Community reportedReported by several players and consistent, but not confirmed by the developer.
Turn controller support off and on again in Steam
Reported to restore correct PS5 prompts by forcing Steam to re-detect the pad. It can also reset your layout, so note your settings first.
Disconnect other input devices
Reported to stop input switching between keyboard and controller. A second connected device is the usual suspect.
Prefer the wired connection for testing
Reported to remove intermittent drift while diagnosing. It does not change mapping.
Unverified
UnverifiedSingle reports. Try these after the official checks, one at a time.
Third-party dead zone tools
Reported to help the drift, but the game then receives altered input, so the result cannot be compared with any official note.
Re-pair the controller from scratch
Occasionally reported to fix mapping. Not confirmed as a cause.
Test a second controller
Useful mainly to rule out hardware. It is a diagnosis step, not a fix.
Do Not Do This First
These make the next comparison impossible.
- Do not stack an external remapper on top of the in-game dead zone setting.
- Do not judge sprint input before updating to the current patch.
- Do not replace hardware before testing with a cable and a second device.
Controller FAQ
Why does sprint keep stopping?
Dead zones and sprint input were adjusted in Hotfix 1.0.2 and again in Hotfix 1.0.4. Update first; neither note claims to fix every sprint problem, so an updated build with the same symptom is still an open case.
Is PS5 button mapping fixed?
No patch note covers it. It was listed in the launch known issues and is still reported by players, so treat it as open and use a workaround.
The camera drifts without touching the stick. Is that dead zone?
Most likely. Dead zones were adjusted twice, so confirm your version and retest before assuming the controller is failing.
My input switches between controller and keyboard on its own. What causes it?
Usually a second connected input device. Disconnect it and retest; the official notes do not cover input switching directly.