Dawnwalker Controller Sprint, Double Input & FPS Fixes

Hotfix 1.0.4 status by symptom

Rebel Wolves released Hotfix 1.0.4 on PC, PlayStation 5 and Xbox Series X|S on September 9, 2026. Its general gameplay notes include controller deadzone and direction-change input adjustments while sprinting.

A separate performance line is explicitly narrower: outdated GameInput controllers should no longer cause FPS drops on Steam. Do not treat that as a universal controller-performance fix for GOG, consoles, Svartrau City or unrelated stutter.

Double inputs, skipped menus and keyboard prompts

Current Steam and Reddit reports describe D-pad presses jumping over menu items, extra inventory inputs, prompts flipping between controller and keyboard/mouse, and controllers not being detected at launch. These reports span more than one controller model, but Rebel Wolves has not published one confirmed root cause or universal fix.

Treat this as a separate diagnostic branch from diagonal sprint interruption and controller-linked FPS loss. A duplicate translation path—such as native game input plus Steam Input or a remapper—is one plausible cause, not a confirmed diagnosis. Several players report that switching Borderless to Fullscreen stopped prompt flipping, while others report no improvement; test it separately and restore the preferred display mode if it does not help.

Safe Steam Input A/B test

Close Dawnwalker before changing the controller override. Connect one controller only and, for the first pass, exit DS4Windows, reWASD or another remapper rather than uninstalling it. In Steam, open Library → The Blood of Dawnwalker → Properties → Controller and note the current override.

For a native Xbox or XInput controller, test Disable Steam Input, restart the game and repeat the same D-pad and inventory actions. If detection or button mapping gets worse, restore the original setting. PlayStation and Steam controllers may require Steam Input enabled. Do not also change deadzones or sensitivity during this comparison, or the result will be ambiguous.

• Record the current per-game Steam Input setting
• Connect one controller and close duplicate remappers
• Change one setting, then fully restart the game
• Repeat the same five menu and D-pad actions
• Restore the original setting if detection or mapping gets worse

PC fix: use Raw or Square stick output

Open the companion app for your controller and find the left-stick circularity, trajectory or deadzone-shape option. Change Circle to Raw, Standard or Square—the exact label depends on the manufacturer. GameSir G7 Pro and Tarantula Pro users independently reported that this restored diagonal movement.

If the controller has no companion option, open Dawnwalker's per-game controller layout in Steam, edit the Left Joystick behavior, set Deadzone Source to Custom and try Square. Do not copy an aggressive inner-deadzone value: the launch evidence supports changing the output shape more clearly than one universal slider number.

• Photograph or note the original controller profile
• Change the left stick only
• Keep the change in a Dawnwalker-specific profile where possible
• Test forward-left and forward-right while holding sprint
• Restore the default layout if the result does not improve

PS5 and Xbox fallback after 1.0.4

First install 1.0.4 and retest with the default 1.00 Controller Sensitivity. If diagonal direction changes still interrupt sprint, lower Controller Sensitivity to 0.80 and repeat the identical route. Rebel Wolves published 0.80 as a temporary launch workaround; it remains a reversible fallback, not proof that the post-patch symptom has the same cause.

Standard PS5 and Xbox menus do not offer the same per-game output-shape control available in some PC utilities. Restore 1.00 if 0.80 only makes the camera slower or does not change sprinting.

• Confirm Hotfix 1.0.4 is installed
• Remove old workarounds and test at 1.00
• Change to 0.80 only if the symptom remains
• Repeat the same forward-left and forward-right path
• Do not replace hardware before testing it in another game

Separate input slowdown from an FPS drop

An input problem changes Coen's gait while the frame rate remains steady. The GameInput case drops frame rate when a controller is connected. Test the same stationary camera scene once with the controller connected and once disconnected; do not compare different locations or combat states.

If the connected-controller FPS drop remains on Steam after 1.0.4, verify that the update completed, restore the default Steam Input profile and record the controller model plus before-and-after frame rate. Do not install third-party driver packages from an unknown source.

Confirm the fix in 60 seconds

Use a quiet open area so combat, stamina and uneven terrain do not confuse the result. Hold the sprint input and rotate the left stick slowly from straight forward through both upper diagonal corners. The workaround succeeds only if Coen keeps a consistent gait through the same angles that previously caused the slowdown.

Confirmed versus provisional

Confirmed: Hotfix 1.0.4 contains controller deadzone and sprint-input adjustments, and the Steam build fixes an FPS-drop cause tied to outdated GameInput controllers. The update is live on PC, PS5 and Xbox Series X|S.

Provisional: current double-input, skipped-menu, controller-detection and prompt-switching reports do not yet have a developer-confirmed common cause. Disabling Steam Input helps some reported native-controller cases and fails to help others. Raw or Square output and the old 0.80 console workaround still apply only to the specific movement symptom they improve.