Rebel Wolves shipped two PC hotfixes inside 48 hours of launch (1.0.2 on September 3, 1.0.3 on September 4) and published a public list of open issues with workarounds on the studio’s X account. This page consolidates the four recurring problems players hit during launch week, what is already fixed, and what still requires a workaround.
If you are troubleshooting right now, the table of contents is built so you can jump straight to the symptom that matches yours.
Quick reference table
| # | Symptom | Affected platforms | Status as of 1.0.3 | What to do |
|---|---|---|---|---|
| 1 | Stuttering in Windowed or Borderless mode | PC | Open (no patch yet) | Launch the game in Full Screen |
| 2 | Crashing while compiling shaders at startup | PC (Intel CPUs most affected) | Open (no patch yet) | Update your BIOS |
| 3 | PS5 / DualSense gamepad button mapping missing | PC (Steam) | Fixed in 1.0.3 | Update the game |
| 4 | Sprint stops when changing direction on a gamepad | PC + console | Partially mitigated (see below) | Lower controller sensitivity from 1.0 to 0.8 in console settings |
The first two items are workarounds because Rebel Wolves has not released a fix yet. The third is fixed in 1.0.3. The fourth is a temporary setting change that smooths the symptom while a game-side fix is in development.
Sources: NerdSchalk (2026-09-03), GamerFuzion (2026-09-04), Kotaku (2026-09-03), Presentation Fire (2026-09-04).
1. Stuttering in Windowed or Borderless mode (PC)
Symptom: The game runs at uncapped frame rate but visibly stutters whenever the player moves the camera or opens menus. Some players report sub-30 fps spikes; others see periodic hitches every 2-5 seconds.
Workaround: Launch The Blood of Dawnwalker in Full Screen instead of Windowed or Borderless mode. GamerFuzion called this “the single highest value change for most people reporting bad performance” because the cost is zero and the change takes ten seconds.
Why the workaround is needed: Windowed Borderless is the default in many Windows installs and most players never change it. Switching to Full Screen bypasses the desktop compositor and gives the engine direct control over the swap chain, which is what the current build is tuned for.
Is a fix coming? As of 1.0.3, Rebel Wolves has not shipped a code change that resolves the underlying Borderless path. Studio X posts only acknowledge the workaround, not a target patch. We will update this page when a real fix lands.
Source: GamerFuzion (2026-09-04) — “the full screen recommendation is the one to try first. It costs nothing, it takes ten seconds, and windowed borderless is the default a lot of people never change.”
2. Crashing while compiling shaders at startup (PC, Intel)
Symptom: The game closes during the first shader compile pass at launch, often before the main menu appears. The error is fatal and reproducible on the same hardware.
Root cause: Outdated motherboard BIOS conflicting with Oodle and Unreal Engine 5 on Intel Core CPUs. Intel identified this class of issue back in 2024, but affected motherboards only get the fix when the user updates their firmware.
Workaround: Update the system BIOS before launching the game. NerdSchalk provides the exact sequence: download the BIOS package for your specific prebuilt PC or motherboard model, follow the manufacturer’s firmware-update instructions, then restart and launch The Blood of Dawnwalker.
Notes:
- AMD Ryzen users have not reported this as widely, but the workaround is harmless on any platform.
- The fix is on the platform side, not the game side, so it is unlikely to ship in a Rebel Wolves patch.
- BIOS menus and update procedures vary by manufacturer. NerdSchalk emphasizes that hardware-specific directions are the appropriate source for the exact steps, not a generic guide.
Source: Kotaku (2026-09-03) — “the studio’s suggested fix is to check that your BIOS is up to date.” NerdSchalk (2026-09-03) provides the step-by-step.
3. PS5 / DualSense gamepad button mapping — fixed in 1.0.3
Symptom: On PC, a PS5 DualSense controller could not be remapped through the in-game controls menu. Buttons that could not be rebound blocked accessibility setups and made the game unplayable for some users.
Fix: Hotfix 1.0.3 (rolled out September 4) added DualSense support on Steam (and GOG). The change is small in scope — a single line in the official patch notes — but it directly resolves the open issue from the day before.
What this does not fix: The change enables DualSense detection, but it does not necessarily add Steam Input re-binding for every action. Players who want full button remapping should still use the Steam Input overlay (Shift + Tab → Controller → Layout) to layer custom mappings on top of the native driver.
Source: GamerFuzion (2026-09-04), confirmed by the Reddit r/DawnwalkerOfficial thread (2026-09-04) and Rebel Wolves’ X account.
4. Sprint interrupt when changing direction (gamepad)
Symptom: On a controller, sprinting stops the moment Coen changes direction more than a small angle. Players describe the effect as “running into a wall mid-dash” and have to re-tap sprint after every turn.
Temporary fix: Change controller sensitivity from 1.0 to 0.8 in the in-game console / controller settings. This does not eliminate the bug but it does reduce the trigger threshold enough that most players can play through without constantly losing their sprint.
Is a game-side fix coming? Yes. Rebel Wolves acknowledged the issue on X and stated they are working on a code fix. NerdSchalk’s quick-answer section notes that “a game update addressing the missing remapping option is in development” — though the language conflates the DualSense and sprint issues, the underlying message is that both are in the queue.
What is still being investigated: Some PC players also report movement input dropping after roughly 10 minutes of controller use, causing running to degrade into slow walking. This is reported as a separate but related controller-input issue. Rebel Wolves has not confirmed a fix timeline as of this page’s last update.
Source: Kotaku (2026-09-03) and NerdSchalk (2026-09-03) for the sensitivity workaround.
What Rebel Wolves has fixed in 1.0.2 and 1.0.3
For completeness, here is what the two launch hotfixes changed beyond the DualSense fix. This information is the verbatim change list from the official patch notes, restated here so the launch-issue context is complete.
Hotfix 1.0.2 (September 3) — quest and input fixes:
- Coen can talk to Farkas now even after killing all the NPCs around him
- Lunka no longer gets lost when leading Coen in the tutorial
- The Uriashi blacksmith learned how to craft a certain holy sword
- Adjustments to controller dead zone and input issues while sprinting, PC only
The Lunka fix is more important than its placement suggests: Lunka is one of Coen’s siblings, and an escort that loses its way during the opening hour is the kind of bug that ends a playthrough before it starts. The Uriashi blacksmith line is phrased as a joke in the patch notes, but GamerFuzion noted that it likely lines up with the “Arbiter’s Blade” achievement, which requires restoring St Mihai’s sword — a blacksmith that could not craft the holy sword would have blocked that quest.
Hotfix 1.0.3 (September 4):
- Added DualSense support on Steam (and GOG)
Source: GamerFuzion (2026-09-04), summarizing the official dawnwalkergame.com/us/en/news/hotfix-102 post.
What to do if you are still stuck
If none of the four workarounds resolves your problem, the most useful next step is to capture the exact crash or stutter moment with the in-game console log (%localappdata%/Dawnwalker/Saved/Logs/) and post it on the official r/DawnwalkerOfficial subreddit. Rebel Wolves’ community team monitors the subreddit for reproducible reports and forwards them to engineering.
For the most up-to-date status on each of these issues, watch the studio’s X account and the dawnwalkergame.com/us/en/news page. This page will be updated as new patches land.
Verified working as of: 2026-09-08. Last reviewed against the studio’s hotfix-102 post and four media walk-throughs of the launch issues. If you find a fact here that contradicts a later official patch note, the official note wins — and we would appreciate the feedback so we can correct this page.
Add a comment (optional)