The Valor Mortis update 1.004 (Version 1.004.000) resolves several critical progression blockers that previously prevented players from completing the main story. This patch is available across PC and consoles, introducing both technical stability improvements and AI fixes.
Critical Progression and Quest Fixes
The most significant changes in this update address bugs that halted campaign progress. Players who were stuck in Chapter 4 following a boss fight will now find that progress correctly saves after the subsequent cutscene. Previously, a failure in the save trigger at this point forced players to repeat the encounter.
Additional mission-related fixes include:
- Chapter 12: A major progression blocker that stopped players from continuing the main story has been resolved.
- Chapter 5: The side quest “In the Name of Art” has been restored. Players can now properly start and advance this questline without it stalling.
Combat and AI Adjustments
Update 1.004 targets the behavior of Volunteer enemies. Before this patch, these enemies could become unresponsive if they were backstabbed while in their patrol state. This fix ensures that the AI properly registers the encounter, preventing static enemy behavior during stealth segments.
Technical and Platform-Specific Updates
For PC players, the update introduces an automatic GPU driver detection system. The game will now check for outdated drivers upon launch and notify the player if an update is required. Additionally, as noted in the SteamDB patch notes, players on Xbox Series X/S should see a resolution to specific graphical issues that affected those platforms.
Players who participated in early Playtest or Demo builds of Valor Mortis are advised to perform a manual configuration cleanup. If you have existing settings files, you should delete the GameUserSettings.ini file located in the following directory:
AppData\Local\ValorMortis\Saved\Config\Windows
This troubleshooting step is recommended for those experiencing settings conflicts, as legacy configuration files from earlier builds can often cause issues in the final release.
