Dawnwalker DualSense Not Working: Steam Input Checks

On this page

DIRECT ANSWER

What the player needs to know

Install the latest Steam update first: Hotfix 1.0.3 adds DualSense support. If your PS5 controller still is not detected, compare a fresh launch with Steam Input enabled and disabled for Dawnwalker only, keeping your original layout. Players report mixed results, so this is a reversible check, not a guaranteed fix. Detection, sprint deadzones and button remapping are separate problems.

Confirmed update1.0.3: Steam DualSense support

Steam Input checkCommunity results differ

ScopePC / Steam detection

Coen faces an axe-wielding opponent in an official The Blood of Dawnwalker screenshot — Coen faces an axe-wielding opponent in official game artwork. This image illustrates the game; the controller checks below are not a hardware test or a settings screenshot.

What Hotfix 1.0.3 confirms

The September 4 Steam announcement lists added DualSense support on PC. It does not document every connection mode, adaptive triggers, haptics or a complete remapping system. Update through Steam before comparing advice written for the launch build with what happens on your installed version.

This guide covers the Steam copy. Do not apply a Steam-specific menu path to the PS5 console version or assume this announcement establishes identical behavior on another PC storefront. If the controller is detected but an action behaves incorrectly, move to the symptom checks below instead of treating all input problems as missing support.

Try a reversible Steam Input comparison

Community evidence is mixed. One post-patch player could launch successfully with Steam Input disabled but needed their Steam layout for custom bindings. Another player said changing the available controller options did not restore detection. Neither account establishes a universal fix, and this site has not reproduced the behavior on controller hardware.

Use the comparison below to isolate a setting, not to replace your layout permanently. Keep the connection and other settings unchanged between attempts so the result is useful.

Finish the game update and close Dawnwalker completely. Record your current per-game controller setting and keep a copy of any custom layout.
First check whether Windows and the Steam controller settings register the device and its inputs. If neither does, troubleshoot that connection before changing game graphics settings.
In the Steam Library, open Dawnwalker’s Properties and Controller settings. Change the per-game Steam Input override, then relaunch from a fully closed game.
Test menu navigation and a simple movement action. Close the game before comparing the other Steam Input setting; do not change global controller settings for every game.
If one setting helps, also check the custom actions you rely on. Restore the original setting if detection does not improve or the layout trade-off is unacceptable.

Detection, sprinting and remapping are different

Hotfix 1.0.2 described PC controller deadzone and sprint-input adjustments. Its known-issues list separately mentioned missing PS5 gamepad button mapping. A working movement stick does not establish that every binding is available, and a later support announcement should not be read as a promise that all three symptoms disappeared.

Choose the check that matches the symptom
Symptom	Useful next check
No controller input in the game	Installed version, device detection, then the per-game Steam Input comparison
Movement works but sprinting stops	Check the installed patch and describe the stick direction; this is not the same as no detection
Input works but custom actions are missing	Compare the active layout with your saved layout; do not assume native support preserves Steam mappings
The game closes or reports an Unreal Engine error	Use the crash guide instead of repeatedly changing controller settings

Troubleshoot an actual crash or stutterMatch the failure to its documented trigger before applying graphics or system changes.Check Swap Weapon versus Draw/Sheathe WeaponA working controller with the wrong action bound needs a control check, not a detection fix.

If neither setting restores input

Restore the original configuration and send a focused report through the official support or Steam discussion channel. Include the game version, Steam version, exact controller model, USB or Bluetooth connection, whether Windows detects inputs, and what changed between the two launches. State whether the failure occurs in menus, during movement or only in one interaction.

Do not delete saves, install an unknown controller DLL or change firmware simply because a forum reply suggests it. The evidence here does not establish those actions as a Dawnwalker fix. Keyboard and mouse can be a temporary option if usable for you, but they do not resolve or disprove the controller problem.

The Steam news API confirms Hotfix 1.0.3 added DualSense support. Two separate player reports disagree on whether changing Steam Input restores detection. The guide therefore offers a reversible comparison, not a guaranteed fix, and separates device detection from sprint deadzones and button remapping. No controller hardware was tested by this site; Bluetooth, haptics and adaptive-trigger behavior remain unverified.

Frequently asked questions

Does Dawnwalker support the PS5 DualSense on Steam?

Yes. The official Hotfix 1.0.3 announcement adds DualSense support on Steam. It does not specify every wireless or haptic feature, and players have still reported detection problems.

Should I disable Steam Input for Dawnwalker?

Try it only as a per-game comparison after updating, preserving your original layout. One player reported restored detection with it disabled; another found controller-setting changes did not help. Restore the setting if it fails or breaks the bindings you need.

Does Hotfix 1.0.3 fix missing button remapping?

The announcement confirms DualSense support, not a complete remapping fix. Test the actions you need separately and keep the distinction between detecting the controller and editing its bindings.

REFERENCE RECORD

Sources used for this page

Official patch notesOfficial Hotfix 1.0.3 Steam announcement, September 4, 2026Official announcement verified through the Steam news API for app 3751260. Confirms added DualSense support on Steam, but does not specify connection-specific features or promise to fix every input issue.Official patch notesOfficial Hotfix 1.0.2 patch notes, posted September 4, 2026Official Steam news post from Rebel Wolves listing the PC-only controller deadzone and sprint-input fix, quest fixes, and the still-open known issues.Community troubleshooting reportPlayer report: Steam Input after the patch, read September 6, 2026One player reports detection returning with Steam Input disabled, at the cost of their custom bindings. This is a reversible diagnostic lead, not an official fix or a universally reproduced result.Community troubleshooting reportPlayer report: Windows sees DualSense but Dawnwalker does not, read September 6, 2026A separate player reports that changing Steam controller options did not restore detection. Used to document mixed outcomes, not to endorse third-party software suggested in replies.

Fix The Blood of Dawnwalker PC crashes tied to FSR frame generation on ultrawide displays and monitoring overlays, with day-one patch context.

Dawnwalker DualSense Not Working on PC