Valor Mortis Crashing, Stuttering and Low FPS

Before you start

Two facts shape everything on this page. First, no patch has been released for Valor Mortis as of October 14, 2026, so there is no fixed build to update to and nothing here can be a fix for a defect the developer already knows about. Second, several of the problems players are hitting are already acknowledged by One More Level — which means they are not your fault and not yours to solve.

That leaves a narrow but real band of things you control. This page stays inside it.

What the developer asks you to do

One More Level's guidance is short, and it is worth following exactly rather than adding to. It asks for two things.

1. Update your graphics driver before launching the game. The developer names both AMD and NVIDIA cards and calls this out before anything else in its post.
2. If the game crashes, submit the crash report and say where it happened. The stated purpose is tracking, not individual support — which means the location matters more than a detailed description of the symptom.

Neither of these is a performance tip. The first is a compatibility requirement, and the second is how a fix gets prioritised in the first place.

AMD Radeon 7000-series

If you are on an AMD Radeon 7000-series card, check the developer's list before you spend time on your own settings. Two cards are named, with no workaround offered.

The developer states it is "actively working with AMD to solve these issues". A graphics driver update is still the sensible first step, since that is what the developer asks for generally — but for these three items the post describes an open problem between the studio and the hardware vendor rather than a user-side misconfiguration.

Shader compilation stutter

A thread in the Steam discussions titled "Compiling shaders overheating the pc" has drawn 38 replies. It was opened on July 29, 2026 — during the open playtest, weeks before release — and was still collecting replies on October 13, release day, so the report predates the launch build rather than being a launch-week artefact. It describes the symptom most commonly reported for this class of problem: heavy load and heat while the game builds its shader cache, usually concentrated in the first sessions.

Two things are worth separating here. The described behaviour is a player report, not a developer statement — One More Level's Known Issues post does not mention shader compilation at all. And the pattern itself is characteristic of games that compile shaders on first run rather than shipping them pre-compiled, where the cost is front-loaded and then stops. That is an explanation of the shape of the report, not a claim about what is happening in this specific build.

Audio cutting out

This is the one problem on the list with a stated response, and the response is unusual enough to quote exactly:

"Audio may cut out on occasion — This should resolve itself if you keep moving through the level"

The suggested action is to keep playing, not to restart the game or change audio settings. If you have already tried resetting your playback device, that is a reasonable instinct that happens to point in the opposite direction from what the developer describes.

Checks you control

These are the steps that are safe, reversible and standard on Steam. None is presented as a confirmed fix for Valor Mortis, because the developer has published no such list.

What not to try

This is the part most pages leave out, and it matters more here than usual because the game is a day old and there is no patch to reason from.

• Do not install a third-party "fix", trainer or performance patch. There is no official mod support and no official tool for changing the game. Anything claiming to fix it is unauthorised, and this site does not host or link such tools.
• Do not assume a crash is your hardware. Several failure modes are on the developer's own list, including a system shutdown on one named AMD card.
• Do not treat a community "performance config" as safe. File edits made against a build that has not yet received a single patch are written blind, and the first official update will invalidate them.

Reporting a crash

The developer's request is specific and easy to satisfy: send the crash report, and say where in the game the crash happened. If you can, add the hardware you are on, since the only hardware-specific items in the official list are AMD cards — being explicit about your GPU is what lets the studio match your report to a known pattern.

For a fast read on whether your problem is official or unofficial, the Known Issues page reproduces the developer's list in full, including which items are still open.