LAUNCH HELP DESK · REPORTS SEPARATED FROM FIXES

Blood of Dawnwalker known issues: bugs, crashes, saves and controller fixes

Use this tracker to match your exact Blood of Dawnwalker problem to the right fix. Start with hotfix status, then choose the crash, save-lock, controller, flickering or stutter guide instead of trying random tweaks.

Last checked: October 9, 2026 · Facts and sources are updated when they change.

CURRENT ANSWER · START HERE

Update first, then pick the guide that matches your symptom. Hotfix 1.0.5 targets shader-compilation stutter for some users. Hotfix 1.0.4 fixes a save blocker, quest progression blockers and Steam FPS drops from outdated Microsoft GameInput. Use can't save, controller movement, flickering or crash and stutter only when that symptom matches.

Start with the symptom that actually matches

Stutter after shader compilationInstall Hotfix 1.0.5, then retest the same scene. It is the current official shader-pipeline improvement, not a universal FPS promise.

Saving is lockedInstall Hotfix 1.0.4 first. If saving remains unavailable after a normal transition, use the save-lock diagnostic and preserve the run.

FPS drops when connecting a controller on SteamHotfix 1.0.4 targets outdated Microsoft GameInput. Retest before applying a Steam Input remap.

Sprint interrupts while turningLower controller sensitivity from 1.0 to 0.8. The dedicated controller guide keeps the PC-only deadzone workaround separate.

Current launch status

Hotfix 1.0.5The latest official update improves the shader-compilation pipeline for some users.

Hotfix 1.0.4It fixes one save blocker, multiple progression blockers and Steam GameInput-related FPS drops when a controller connects.

Developer acknowledgedThe earlier official known-issues post includes Windowed/Borderless stutter, shader-compilation crashes and PS5 button mapping; check the current patch note before assuming each remains unresolved.

Repeated reportPlayers report startup black screens, cutscene crashes or crashes returning at the same scene.

Performance reportsFrame pacing and a 30 FPS cinematic cap are reported; results vary by system and scene.

Visual reportsPC shimmer, light flickering and PS5 Pro VRR reports have a separate platform-specific diagnostic guide.

Controller movement: the clearest reproducible workaround

First lower controller sensitivity from 1.0 to 0.8, as listed in the developer Known Issues thread. If diagonal turning still interrupts sprint on PC Steam, use the dedicated illustrated controller movement guide for the additional Square-deadzone path.

The sensitivity setting is the developer-listed temporary workaround. The Square/Raw remap remains a separate community workaround and the Steam steps do not apply to console system settings.

Startup crash, black screen or repeatable cutscene crash

  1. Record the failure: platform, game version, storefront, GPU driver, exact scene and whether it fails at the same point.
  2. Restart once: close the game and storefront completely, then retry without adding mods or launch arguments.
  3. Verify the installation: use the storefront's file verification feature. This is a safe integrity check, not a guaranteed fix.
  4. Remove one variable at a time: disable overlays or third-party injectors temporarily, retest, and avoid changing several graphics or system settings together.
  5. Stop after repeatable failure: preserve the crash report and wait for an official update instead of applying unrelated registry edits, driver downgrades or copied configuration files.

Stutter, low FPS and 30 FPS cutscenes

Early results are mixed: some players report smooth play, while others report camera-turn or traversal stutter on high-end hardware. A technical report also describes a 30 FPS cinematic cap. That makes system + settings + scene + patch version essential context.

  • Do not call every low frame rate a bug before comparing resolution, preset, DLSS/FSR mode and Frame Generation state.
  • Do not promise that shader-cache deletion, a mod or a hidden configuration line fixes every system.
  • For a useful benchmark, include average FPS, frame-time behavior and the tested location—not only the GPU name.

Controller menus, wrong button prompts and wireless detection

These may be separate from the movement deadzone symptom. Players report selections jumping, confirm buttons failing, input switching between mouse/keyboard and controller, Xbox glyphs with DualSense, or wireless detection problems. Test one controller, one connection method and one Steam Input state at a time, and report the exact combination.

Torch and audio bugs: report the symptom before changing settings

A missing torch effect, incorrect sound, silent dialogue or intermittent audio can come from different systems. Record the exact location, quest state, platform, patch, output device and whether a restart reproduces it. Check the current patch notes before changing unrelated graphics, controller or audio settings, then submit a short reproducible report if it persists.

Official fix versus community workaround

Official fixA dated publisher or developer patch note identifies the issue and changed version.

Community workaroundReversible steps are reproduced by independent players but not confirmed by the developer.

Repeated reportMore than one player describes the same symptom, but the cause and solution remain unknown.

Unverified claimA single unsourced comment, copied fix list or video without platform and version context.

Before submitting a report

Include platform, storefront, game version, controller or hardware model, graphics settings, steps to reproduce and a short clip where possible. Use the structured feedback form without account credentials, personal information or private save files.

Sources