The Blood of Dawnwalker shipped worldwide on September 3, 2026 on PC, PlayStation 5, and Xbox Series X|S. Bandai Namco and Rebel Wolves confirmed a major day-one patch dropped alongside the game, addressing the most-discussed pre-release concerns: the console performance modes that were missing from the late-August review build, the PS5 Pro enhancements promised by the launch trailer, and PC frame generation support.
This page is the citable known-issues hub. It pairs with the per-patch changelog entries in the Updates Archive for full technical detail, and with The 30-Day Time Mechanic Explained for understanding why some of the launch-day fixes matter to quest progression.
What The Day-One Patch Fixed
The day-one patch was version 1.003.000, the same number carried in the Steam build at launch. The big-ticket items, per Bandai Namco’s launch press release and the asumetech mirror of the patch notes:
- Performance Mode — 60fps on PS5 and Xbox Series X|S, the mode the late-August backlash was about and the reason Rebel Wolves went back to the engine to add it.
- Balanced Mode — 40fps for 120Hz VRR-capable displays, the headline new option for owners of VRR TVs and monitors.
- Quality Mode — 30fps with lighting, shadows, and draw distance pushed to maximum.
- PS5 Pro enhancements on top of all three modes, using PSSR (PlayStation Spectral Super Resolution) for cleaner image reconstruction.
- NVIDIA DLSS Frame Generation for RTX 40-series and 50-series cards on PC.
- AMD FSR Frame Generation for everyone else — Intel Arc, AMD Radeon, older NVIDIA hardware including RTX 30-series, and integrated GPUs.
- Frame rate limiter for FSR users, with a DLSS-compatible limiter promised in a later patch.
The patch download size is roughly 4.2 GB on PS5 and PS5 Pro, 5.1 GB on Xbox Series X, and 3.8 GB on PC.
For full technical detail and the studio’s own launch-day quote from Konrad Tomaszkiewicz, see Launch Day: September 3, 2026 Ship + Day-One 1.003.000 Patch Drops.
Documented Launch-Day Issues
The launch-week issues below are the ones the community catalogued in the first 72 hours of play, organized by status as of the most recent confirmed patch. Sources: the Steam Community announcement threads for each hotfix, with the Reddit r/DawnwalkerOfficial thread consensus as the upvote filter for “this affects enough players to matter.”
| Issue | Status | Where Reported |
|---|---|---|
| Coen skips the Errant Sigil pickup during the Sacred Covenant quest | Fixed in 1.0.4 | Steam Community, r/DawnwalkerOfficial |
| RTX 30-series frame-pacing issues | Improved in 1.0.5, full fix pending | Steam Community, r/DawnwalkerOfficial |
| Crash on Chapter 2 entry (post-prologue) | Fixed in 1.0.4 | Steam Community, Twisted Voxel coverage |
| Audio stutter during combat transitions | Fixed in 1.0.4 | Steam Community |
| Save file corruption after 8+ hour sessions | Fixed in 1.0.4 (not retroactive — affected saves unrecoverable) | Steam Community, r/DawnwalkerOfficial |
| FSR Frame Generation crash on ultrawide monitors | Open — known limitation in 1.003.000, follow-up hotfix planned | Steam Community |
| Steam Input button mapping missing for PS5 gamepad | Open — separate from 1.0.3 DualSense plugin fix | Steam Community |
The save-corruption fix in 1.0.4 was the headline community concern. The bug was a silent fail of the save button after certain triggers, most commonly dying during the prologue boss fight against Brencis. Rebel Wolves has explicitly said the fix is not retroactive — saves created before the patch remain unrecoverable in that state, so anyone sitting on a broken save should reload a pre-prologue checkpoint rather than wait for a back-port. The full patch detail is in Hotfix 1.0.4.
Workarounds For Open Issues
Three of the open launch-day issues are not yet fixed in any shipped patch. The workarounds below are the studio’s recommended temporary fixes from the Steam Community Known Issues section.
FSR Frame Generation crash on ultrawide monitors. The bug only fires when FSR Frame Generation is enabled on any aspect ratio other than 16:9. Workaround: switch to native DLSS if you have an RTX 40- or 50-series card, or run the game at native resolution with no upscaling until the follow-up hotfix ships. Switching between DLSS, FSR, and native rendering requires a full game restart for the engine to re-initialize its upscaling state.
Steam Input button mapping missing for PS5 gamepad. This is a Steam Input issue, separate from the DualSense plugin fix in Hotfix 1.0.3. Hotfix 1.0.3 routed the DualSense controller through Sony’s HID layer so the adaptive triggers register as analog input with proper resistance curves, but it did not add the Steam Input button-remap surface. Workaround: use the DualSense plugin without remapping, or temporarily bind inputs through Steam’s legacy Big Picture mode.
Sprinting sticks with a gamepad on console. Players on PS5 and Xbox found that sprinting could stop when changing direction with a gamepad. Rebel Wolves’ temporary workaround is to drop controller sensitivity from 1.0 to 0.8 in the system settings. A proper fix is planned for a later hotfix.
Shader compilation crash on launch. From the 1.0.2 Known Issues list: a small number of players reported a crash on compiling shaders during the first engine boot. Workaround: confirm your motherboard BIOS is up to date before launching. The crash rate is significantly higher on systems running BIOS versions from 2023 or earlier.
Windowed or Borderless display mode stutter. From the same 1.0.2 Known Issues list. Workaround: launch in Full Screen mode. The stutter is much smaller in Full Screen, and the day-one 1.003.000 patch did not fully resolve it for windowed players.
How The Patch Cadence Is Tracking
As of this writing, Rebel Wolves has shipped five patches in the first seven days post-launch:
- 1.003.000 (Sept 3) — Day-one, console performance modes, DLSS + FSR Frame Generation, PS5 Pro enhancements.
- 1.0.2 (Sept 3, same day) — Quest fixes (Farkas dialogue, Lunka tutorial pathing, Uriashi holy sword recipe) and PC controller dead zone adjustment.
- 1.0.3 (Sept 4) — Steam-only DualSense plugin via Sony HID.
- 1.0.4 (Sept 9) — Nine quest blockers fixed (Hive and Seek, Deep Down, On the Run, Smoke and Ashes), save-game blocker resolved, red pipe asset pulled.
- 1.0.5 (Sept 10) — Shader compilation pipeline rework for stutter, scoped to performance only.
The pattern is a two-track cadence: small quest / save / controller fixes every other day, plus targeted performance patches as telemetry accumulates. The studio’s launch posture is patching in public with specific bug names attached to specific fixes, which is healthier than the late-August performance conversation suggested. The next patch entry on this wiki will likely land as 1.0.6 addressing the open ultrawide and Steam Input issues above.
For the per-patch changelog detail, see Hotfix 1.0.2 and 1.0.3, Hotfix 1.0.4, and Hotfix 1.0.5: Shader Compilation Pipeline Rework.
What’s Coming Next: October Patch Preview
Rebel Wolves has now outlined the first major post-launch update. Director Konrad Tomaszkiewicz confirmed the scope in a Eurogamer interview published September 21, 2026, with GamesRadar+, Kotaku, GamerFuzion, TweakTown, and Rock Paper Shotgun confirming the same detail set within 48 hours. The patch is expected “in the beginning of October,” with no exact date yet, and is being described as “the big patch which will deliver a lot of upgrades.”
Key items relevant to this known-issues hub:
- Difficulty rebalance. A new easiest tier takes over the Story label, and the current Story is being renamed (working name “Demanding”). Existing Story players keep their difficulty — the setting just gets a new label and moves up one notch in the list. Five difficulty tiers total after the patch: Story, Demanding, Fair, Challenging, Duelist.
- Combat stun target-switching removed. When Coen stuns an enemy, the lock will no longer jump to a different target automatically. To compensate, a stunned enemy will now take three hits before the stun breaks. This is the most-discussed combat fix from launch-week Steam reviews.
- Combat escape rewrite. Running or fleeing from combat will ignore the navigation mesh, so Coen stops snagging on scenery. Aggressive wildlife is also being reworked so a missed attack in wolf form or witch-sprint does not drag Coen into a fight.
- PC performance work continues. The director acknowledged the stutter complaints and confirmed optimization is ongoing, but explicitly did not promise that the October patch resolves shader-compilation stutter for all hardware. Treat this as a separate line from the 1.0.5 shader pipeline rework.
- Not in this patch. Enemy health tuning (rejected by the studio, who attribute perceived sponginess to player build), 30-day timer changes, ultrawide / Steam Input fixes, and the still-open shader crash list above.
- Being explored for later patches. New Game Plus (director: “there is a chance but I don’t want to speak about it yet”) and additional enemy types.
The detailed writeup with the full Eurogamer quote set and per-outlet coverage is in October Patch Preview.
Honest Gaps
- Per-issue upvote counts are not pinned. Reddit thread ranking shifts day to day; the Steam Community threads pin more reliably. The “consensus” framing here is “dev-confirmed or replicated by enough players to be cited,” not a strict upvote threshold.
- 1.0.6 / October patch scope confirmed, no ship date. Rebel Wolves has now publicly outlined the October patch (new easiest difficulty tier, stun target-switching removed, navigation mesh fix for combat escapes, ongoing PC performance work). See October Patch Preview for the full scope. The studio has not yet committed to a specific ship date — Tomaszkiewicz said only “the beginning of October.”
- Some launch-day issues may have been resolved by patches after publication. This page tracks the issue status as of the most recent confirmed patch noted above. Check the Updates Archive for entries beyond 1.0.5.
- The Bandai press release wording is the primary source for “major day-one patch.” That phrase is the studio’s own framing, not a community characterization. Direct quote from the September 3 launch press release is available via the Launch Day update entry in the Updates Archive.