Skip to content
Dawnwalker Guide
Powered by Pagefind
Guides

The Blood of Dawnwalker Hotfix 1.0.2 & 1.0.3 Patch Notes

Official Hotfix 1.0.2 and 1.0.3 notes for The Blood of Dawnwalker, covering quest fixes, PC controller support, and workarounds.

9/4/2026 Dawnwalker Guide Editorial Last verified: 9/6/2026 6 min read

FAQ

Which platforms received Hotfix 1.0.2?
The official notice says Hotfix 1.0.2 is out on PC, PlayStation 5, and Xbox Series X|S.
What should I do if the game stutters in Borderless mode?
The developer lists Windowed and Borderless stuttering as a known issue and recommends trying Full Screen as a workaround.
What does Hotfix 1.0.3 add?
The official Steam announcement says Hotfix 1.0.3 is rolling out on PC and adds DualSense support on Steam.

Hotfix 1.0.2 at a glance

Rebel Wolves published Hotfix 1.0.2 on September 4, 2026, one day after the game’s public launch. The notice confirms that the build is available on PC, PlayStation 5, and Xbox Series X|S. A separate Steam announcement then recorded Hotfix 1.0.3 for PC. These are focused launch fixes rather than content expansions: the listed changes target quest states, controller input, and device support. The 1.0.2 notice also records issues that the team is still investigating.

Use this page to check whether a reported problem is already acknowledged. Let your platform finish installing before comparing build labels, and see our Release Date & Global Unlock Guide for launch details.

Hotfix 1.0.3: DualSense support on PC

The latest Steam Community announcement says Hotfix 1.0.3 is being rolled out on PC and adds DualSense support on Steam. The notice lists no quest changes, balance adjustments, performance targets, or console rollout. Treat it as a small controller-compatibility update and let Steam complete the download before testing a DualSense pad.

This distinction matters when reading the 1.0.2 known-issues list. The earlier notice mentioned a missing button-mapping option on a PS5 gamepad; 1.0.3 confirms Steam DualSense support on PC, but it does not state that every console mapping limitation is fixed. Keep the platform and launcher in any support report.

Quest fixes

The first group of changes addresses progression and interaction conditions. These fixes matter because a quest can appear blocked even when the player has completed the expected combat or tutorial step.

Coen can speak with Farkas after the surrounding NPCs die

Before this hotfix, the official notice indicates that killing every NPC around Farkas could prevent Coen from talking to him. Hotfix 1.0.2 specifically restores that conversation condition. If you cleared the area before speaking to Farkas, return to his location after the update and try the interaction again rather than immediately loading an earlier save.

This fix does not promise that every unrelated quest state will repair itself. If the conversation is still unavailable, record the exact objective text, your platform, and the build shown by the game. A reproducible report is more useful than assuming that a different choice or an unlisted item is required. Our Walkthrough Hub will only add route instructions after they have been tested against a released build.

Lunka no longer gets lost during the tutorial escort

The second quest fix concerns Lunka while she is leading Coen in the tutorial. The official wording says that Lunka no longer gets lost in this sequence. This is especially useful for players following the opening route, because an escort character disappearing can look like a missed trigger or an incorrect direction.

If you are replaying the opening, keep the objective active and follow the normal tutorial route first. If Lunka still fails to move, pause and confirm that the hotfix has finished installing, then reload a save made before the escort began. Our illustrated Prologue Walkthrough covers the opening sequence without treating an unverified workaround as a required step.

Uriashi’s blacksmith can craft a certain holy sword

The third quest-related note says that Uriashi’s blacksmith has learned how to craft a certain holy sword. The notice does not name the sword, list its materials, or describe a new recipe interface. For that reason, this page does not invent a weapon name or claim a specific stat change.

After updating, visit Uriashi again if the relevant objective is active and check the blacksmith menu. If the recipe is still unavailable, capture the displayed requirements and current quest state before reporting it. Recipe availability can depend on progression, while the hotfix note only confirms that the blacksmith’s missing knowledge was corrected.

PC controller adjustments

The gameplay section contains one platform-specific entry: PC-only adjustments to controller dead zone and input issues while sprinting. A dead zone controls how far an analog stick must move before the game registers movement. Reducing an unwanted dead zone can make small camera or movement corrections feel more responsive; changing it too far can also make drift more noticeable. The official notice confirms that adjustments were made, but it does not publish recommended values.

Players using a controller on PC should therefore test movement in a safe area before changing several settings at once. Check ordinary walking, camera control, and sprint activation separately. If sprinting still drops inputs, note whether the issue appears with a wired or wireless connection, which controller layout is selected, and whether another input device is connected. Those details help separate a remaining game issue from an operating-system or device-layer conflict.

Console players should not assume that this specific input line applies to them: the note labels it PC ONLY. The same page separately lists a PS5 gamepad mapping limitation under known issues, described below.

Known issues and official workarounds

The developer is still investigating three problems. They are not listed as fixed by Hotfix 1.0.2, so treat the following as current workarounds rather than permanent solutions.

Stuttering in Windowed or Borderless mode

The official recommendation is to try Full Screen if the game stutters in Windowed or Borderless mode. Change one display mode at a time, restart the game, and compare the result in the same location. Keep a note of your original setting so you can switch back after a later update.

Crashes while compiling shaders

For crashes during shader compilation, the notice asks players to check whether their BIOS is up to date and links to RAD Game Tools’ Oodle Intel information. A BIOS update is hardware-specific and can carry its own risk, so use your motherboard manufacturer’s instructions and do not treat an unrelated download as an official fix. If the crash persists, include your CPU, motherboard, BIOS version, GPU driver, and the exact point at which compilation fails in a support report.

Missing PS5 gamepad button mapping

The final known issue is a missing option to map buttons on a PS5 gamepad. Hotfix 1.0.3 adds DualSense support on Steam for PC, but the official notices do not provide a console remapping method or a release date for a broader mapping option. Do not promise a menu path that is not present in the official notices; record the controller model, launcher, and game version instead.

What to verify after installing

  1. Confirm that the platform has completed the hotfix download and any restart requirement.
  2. Re-test Farkas, the Lunka tutorial escort, or Uriashi only if one of those situations affected your save.
  3. On PC, test controller movement and sprint input before changing multiple settings.
  4. If troubleshooting, save the platform, build label, quest objective, and exact reproduction steps.
  5. Check the Guides Index for future versioned notes; we will update this page only when a first-party change or a reproducible test supports it.

Source and editorial boundary

The confirmed facts come from the official Hotfix 1.0.2 notice, dated September 4, 2026, and the official Hotfix 1.0.3 Steam announcement. They do not publish a recipe name, controller values, or a schedule for the remaining issues, so those details remain open pending testing.

Related guides

Was this helpful?