Update the demo, update your GPU driver, restart the game, and avoid FSR on an affected Nvidia GPU. If loading still fails, verify that Valor Mortis is using the discrete GPU. For a missing interface, toggle HDR off and on.
The developer’s June 11 pinned list still warns that enabling DLSS may freeze loading, while the June 10 version 1.02 post says “DLSS is Back” and makes DLSS 4.5 available. We therefore do not label the freeze universally fixed. If DLSS freezes on your system, use TSR, restart, and report it.
Do these four things first
- Install the latest Steam update. Demo 1.01–1.03 fixed crashes, stuck states, progression limits, and a Witch Hunt loading crash.
- Install the current stable GPU driver. The developer specifically warns that older Nvidia drivers have caused poor performance.
- Restart after changing Frame Generation. Version 1.02 says an Unreal Engine limitation requires a game restart after enabling it.
- Change one setting at a time. Keep a record of the upscaler, Frame Generation, HDR, preset, and display mode that triggered the problem.
Crashes and loading problems
Nvidia GPU crash with FSR selected
Official status: known issue. Some Nvidia users may crash during level loading when FSR is selected.
Official workaround: use TSR or DLSS until the issue is resolved. For recovery steps when the game no longer reaches the menu, use our dedicated FSR crash guide.
D3D12 / D2DX12 crash or wrong-GPU launch
Official workaround: make sure the game runs on the main/discrete GPU rather than integrated graphics. Nvidia users can set this in Nvidia Control Panel. The developer also suggests disabling Intel(R) AI Boost through Device Manager.
Because disabling a device affects the system, try explicit high-performance GPU selection first and change only the item named by the developer.
AMD crash mentioning amdxc64.dll
Official workaround: perform a clean driver reinstall. The pinned thread says the file may be missing or corrupted for affected AMD users.
DLSS freezes while loading
Status: still listed in the pinned Known Issues thread, although 1.02 restored DLSS support. If it occurs, switch to TSR, restart the game, and submit a report. Do not keep force-closing repeated loads with the same setting.
Black or endless loading screen
Official status: a rare black/loading-screen lock is acknowledged, but the pinned thread gives no dedicated fix.
Safe fallback, not an official guarantee: fully restart the game, update the demo and driver, turn off the upscaler/Frame Generation combination that preceded the lock, and retry with TSR. If Witch Hunt alone fails, confirm version 1.03 is installed because that patch fixed a Witch Hunt loading crash.
Display, UI, and graphics issues
| Issue | Status / action |
|---|---|
| Cursor or UI buttons missing with HDR | Official workaround: turn HDR off and on. |
| Game moves to another monitor after Fullscreen | Known issue. The developer lists no fix; use Windowed or Borderless as a reversible fallback. |
| Visual artifacts on Epic preset | Known issue. Lower the preset as a reversible fallback and report the GPU/driver combination. |
| Ray tracing unavailable | Officially disabled/temporarily not working in the demo; there is no user-side unlock to recommend. |
| Crash when choosing Exit Game | Known issue. This occurs on exit and is not evidence that save/progression was repaired or lost. |
Known gameplay and localization issues
The developer also lists these current demo defects. They do not all have user-side fixes:
- Dog enemy sliding during the bark animation, missing grab audio, and ragdoll glitches.
- Climbing animations that are not final.
- Small glitches while switching weapons.
- Depleted consumables disappearing from the HUD.
- Critical/finisher animations not snapping correctly.
- Running enemies clipping through assets and teleporting close to the player.
- The musket jump attack not working.
- Rare looping audio after an enemy dies.
- Missing text or poorly adjusted UI in non-English languages.
What patches 1.01–1.03 say they fixed
| Version | Developer-listed fixes most relevant to players |
|---|---|
| 1.01 | Memory/progression crashes, tutorial-screen crashes, Chapter I geometry traps, Chapter I and Lothaire performance, Lantern consistency. |
| 1.02 | Crashes tied to player events and specific blocks, stuck after respawn, progression cap, Mice dialogue, skybox/blood VFX, loading-screen jumps; DLSS 4.5 and XeSS 3 available. |
| 1.03 | Witch Hunt loading crash, corrupted blood VFX crash, audio-loop mitigation, GPU auto-detection, and continued performance work. |
A patch note that says a crash was fixed does not prove every visually similar crash has the same cause. If the problem continues on the current version, report it with the exact level, settings, and hardware.
How to report a useful bug
- Confirm the current demo version and Steam update status.
- Record CPU, GPU, driver version, RAM, display mode, HDR, graphics preset, upscaler, and Frame Generation.
- Write the level and last action before the issue.
- State whether it reproduces after a restart and after changing only the suspected setting.
- Use the in-game crash reporter when it appears, then post in the official Steam feedback forum.
Official sources
- Known Issues [Demo] — developer-pinned Steam thread, last edited June 11, 2026.
- Official Valor Mortis Steam news, including Demo Hotfix 1.01 (June 8), 1.02 (June 10), and 1.03 (June 12).
- Official Steam store page — current Windows and hardware requirements.