The Blood of Dawnwalker known issues — the shader crash is your CPU, not your GPU

Rebel Wolves' official known-issues list plus the workarounds: borderless stutter, the shader-compilation crash traced to degraded Intel 13th/14th-gen chips, controller sprint drop, and what Hotfix 1.0.4 actually fixed.

Checked in-game on patch 1.0.4

Start with build version

Everything below is against the game as patched by Hotfix 1.0.4, released 9 September 2026. Several of the worst-reported problems — being trapped inside a house, saving being blocked, quest softlocks — were fixed there. Verify your version before debugging anything, because half of the threads you will find are describing pre-1.0.4 behaviour.

The four issues Rebel Wolves listed officially

Published 3 September 2026:

IssueStatus thenWorkaround as given
Stutter in windowed / borderlessKnownLaunch in fullscreen
Crash during shader compilationKnownUpdate your BIOS
PS5 controller button remapping options missingIn progressNone offered
Sprint cuts out when changing direction on controllerIn progressDrop controller sensitivity from 1 to 0.8 in console settings

The shader crash deserves its own section

This one gets misdiagnosed constantly, because it presents as a GPU fault and is not one.

The mechanism the developer points at: a hardware problem affecting Intel 13th and 14th generation Core processors (13xxx and 14xxx series). Silicon degradation on those chips causes Oodle data decompression to fail, which crashes Unreal Engine-based games. The common failure signature in Unreal titles is DecompressShader(): unable to decompress shader with GetShaderCompressionFormat=Oodle.

Two things make this extra confusing if you are hunting it:

  • It is not limited to Oodle. Any heavily-multithreaded program can trigger it on an affected chip, so the crash may not look game-specific.
  • It can surface as a false "out of video memory" error. People buy a new GPU for a CPU fault.

The action is a BIOS update from your motherboard vendor, which ships microcode to stop the operating conditions that cause the damage. If degradation has already happened it is not reversible, and the part needs replacing.

What Hotfix 1.0.4 fixed

Small patch, no new content, but it went straight at the complaints that generate guide searches:

Stability and progression

  • Tutorial no longer stalls if you use the devour bite too quickly
  • Coen no longer gets trapped inside certain houses
  • Fixed a bug that prevented saving
  • Fixed blocking being disabled under some conditions
  • The training-sequence NPC can now be spoken to during sparring

Quests

  • Orcha no longer attacks Coen while being assaulted by guards
  • Coen no longer gets stuck in a cave during the "Deep Down" quest
  • Muroman no longer fails to spawn
  • "Hive and Seek" no longer ends prematurely in some cases
  • Advancing "On the Run" no longer causes an infinite loading loop
  • Lone Wolf's Hunt now displays the difficulty level correctly
  • Softlock after tailing Sara fixed
  • Investigating the rag is now optional during "Ash and Bone"
  • Fixed a blocker in the "What the Heart Wants" quest

Other

  • Coen and Yorg now drink from a cup at low quality settings
  • Removed an incorrectly used red-pipe asset
  • Fixed the prologue music cutting out
  • Torch props no longer growing uncontrolled
  • Steam-only: connecting a controller through the outdated GameInput software no longer tanks framerate
  • PC: fixed VSync behaviour when using FSR frame generation

PC requirements, if you are deciding whether to bother

Final published numbers assume DLSS, FSR or XeSS enabled:

TargetCPUGPUVRAM
1080p/30 low (minimum)i5-11400F / Ryzen 7 2700XGTX 1060 / RX 5806 GB
1080p/60 mediumi7-11700K / Ryzen 7 5700XRTX 2060 Super / GTX 1070 Ti / RX 5700 / Arc A7508 GB
1440p/60 high (recommended)i7-11700K / Ryzen 7 5700XRTX 4060 / RX 7600 XT8 GB
4K/60 ultrai7-12700K / Ryzen 7 7800X3DRTX 4070 Ti / RX 9070 / Arc B58012 GB

Worth noting: these were lowered close to launch. The earlier April document demanded an RTX 5090 for 4K/60 and a 12 GB minimum on the recommended tier. All four targets need 60 GB of SSD.

Patch timeline, so you know what you are on

BuildDateWhat it was
1.0.25 September 2026Quest and controller fixes (below)
1.0.49 September 2026Stability, save-blocked, house-trapped, quest softlocks
October majornot shipped as of 4 October 2026New easiest difficulty, targeting rework, disengage, PC performance

What 1.0.2 fixed

Worth listing because these still show up in threads written before 5 September:

  • Coen can now talk to Farkas even after killing every NPC around him
  • Lunka no longer gets lost while leading Coen during the tutorial
  • The Uriashi blacksmith can no longer fail to craft one specific holy sword
  • PC-only: controller deadzone and sprint input issues addressed

And note the three items the studio flagged as under investigation at that point — windowed/borderless stutter, shader-compilation crash, missing PS5 controller remapping. Those are the same three that got the 3 September workaround post, which is how you can tell the workarounds below were still the live answer.

Coming in the October update

Announced for early October, still undated as of 4 October 2026: an additional, easier difficulty tier because demand was heavy, with the current Story mode repositioned as a harder setting; a smoother way to disengage from combat when you cannot win it; target lock and camera work; performance improvements with PC called out specifically; New Game Plus confirmed as planned but not yet delivered.

If your complaint is difficulty rather than stability, that is the patch to wait for rather than a mod.

⚠️ One item above is quoted from a translated changelog where the character name did not localise cleanly, so treat that NPC name as unverified. The October update has no confirmed release date — do not publish one.

People also ask

My game crashes while compiling shaders. Is my graphics card failing?
Almost certainly not. The official known-issues post points this at a hardware problem affecting Intel 13th and 14th generation Core chips, where degradation causes Oodle data decompression to fail inside Unreal Engine builds. The recommended action is to update your motherboard BIOS. Unreal games commonly surface this as a DecompressShader failure, and it can even report as an out-of-video-memory error that is actually CPU-caused.
The game stutters in borderless window. Is that normal?
It is on the official known list. The workaround given by the developer is to launch the game in fullscreen instead.
My controller stops sprinting when I change direction.
Also listed as known and unrepaired at the time of that post. The workaround offered was dropping controller sensitivity from 1 to 0.8 in the console settings.
I got stuck inside a house and could not save. Was that a bug?
Yes, and both were fixed in Hotfix 1.0.4 on 9 September, along with a tutorial stall and several quest softlocks. Confirm your build version before spending time on this class of problem.

Sources & version history

External claims on this page trace to the items below. Anything we could not confirm is written as a question, not a fact.