Valor Mortis Known Issues and Fix Status

Status at a glance

Valor Mortis released on October 13, 2026. On the same day, the developer posted a Known Issues thread on Steam listing the problems it already knew about. As of October 14, 2026, no patch had been published for the game: the official Steam announcements feed carries no patch note, and no patch thread appears in the Steam Discussions.

AMD Radeon 7000-series

This is the most specific part of the developer's post, and it names the affected hardware rather than describing it vaguely. Quoted from the post:

• Radeon RX 7600 — "System shutdown can occur while playing".
• Radeon RX 7900 XT — "GPU crashes may occur during gameplay".
• AMD Anti-Lag 2 — "may not work properly".

The developer states it is "actively working with AMD to solve these issues". There is no workaround listed for any of the three, which is the honest reading: for these specific problems the developer's position is that it is still an open matter between it and AMD.

Audio, performance and crashes

Three items sit in this band, and only the first has anything resembling guidance attached.

The audio note is the only item in the whole post where the developer offers an in-game action rather than a software fix, and it is worth taking at face value: the suggested response is to keep moving, not to restart.

Gameplay issues and workarounds

This is where the post becomes genuinely useful, because three of the six items come with a stated workaround. These are reproduced exactly, including which one is a soft-lock.

The Caverns entry is the one that blocks progress rather than merely annoying you, and it is the reason this page exists in the shape it does: the fix is navigation, not settings. Note the wording — the developer says the player "may not be automatically returned", so the manual teleport is the intended recovery rather than a misuse of the map.

Visual issues

Four cosmetic or display problems are listed. None of them blocks play, which is why they sit last in the developer's own post as well.

• UI text can overlap for some non-English characters. This affects the 13 non-English interface languages the store lists, not English.
• Skin previews in the Arsenal may appear in low resolution the first time you hover over them — described as a first-hover problem, so it resolves after the asset loads.
• Assets may visibly reload after changing graphics settings from the Pause Menu on some levels — the developer scopes this to "some levels".
• Screen artifacts may appear when using bayonet melee attacks with the musket — explicitly "on rare occasions".

How to confirm the patch state

There is no version number for this page to quote, because One More Level has not published one and the launch build has not been replaced. That makes the check simple rather than obscure.

1. Open the game's page in your Steam library and look at its update history in the properties panel. A patch would appear there as a download.
2. Read the Steam announcement feed for the game. A patch note would be posted there, and none has been as of October 14, 2026.
3. Re-read the developer's Known Issues thread. If an item is fixed, the post is the place it would be acknowledged.

Until one of those three changes, the list above is still current and there is nothing to install. This page will be wrong the moment a patch lands, which is why it carries its check date.

Reporting a problem

The developer asks for two things specifically, and they are the two most useful pieces of information a report can carry: the crash report itself, and where in the game it happened. The studio's wording is that it wants to "track it down", which means a location is more valuable to it than a description of the symptom.

If your issue is not on the list above, it is still worth posting — a maintained Known Issues thread is evidence that the developer reads that forum. What is not worth doing is installing a third-party "fix". There is no official patch to replace, no official tool for modifying the game, and no patch notes to reverse-engineer. The performance troubleshooting page covers the checks you control, and stays inside them.