Read the configuration and target together
The Steam page lists a processor pair, a graphics-card pair, memory and system requirements as one minimum specification. Its additional note then identifies the visual and frame-rate target associated with that configuration. Treating the components and target together is more precise than describing the hardware as suitable for every resolution and preset.
The target explicitly includes Low settings and upscaling. Those qualifiers belong to the requirement, rather than an optional detail to drop when comparing another computer. The current published specification therefore answers the minimum-running question without offering a guarantee of native-resolution high-refresh performance.
Use the current 60 GB SSD requirement
The current page and the official store API agree on sixty gigabytes of available storage and an SSD requirement. This is the requirement retained from the research after conflicting early specifications were rejected. The page’s published target is also consistent between those two representations of the same official dataset.
Their agreement is a useful consistency check, rather than two independent hardware tests. The developer’s patch notes provide additional context about autodetection and optimization but do not replace the specification table. The following sections keep the current minimum separate from historical demo-performance work.
The current PC minimum requirements
The current Steam minimum lists Windows 10, a Ryzen 5 3600 or Core i5-10600K, and 16 GB of RAM. Its graphics requirement is an RX 5600 XT or GTX 1660 Ti, with DirectX 12. These components should be read together as the published minimum configuration, rather than choosing one requirement and treating it as the whole performance target. The listed alternatives are the publisher’s specified processor and graphics examples, not a comprehensive ranking of other components by expected performance.
Steam specifies 60 GB of available storage and requires an SSD. The accompanying target is 30 FPS at 1080p on Low with upscaling, which is more precise than a general claim that the game will run. The retrieved official listing supplies that minimum target; it does not provide a verified higher-resolution or high-refresh benchmark for every other configuration. An SSD and the stated settings target are part of the same published requirement, so they belong alongside the headline memory and graphics information.
Upscaling support in the demo patches
The June version 1.02 demo hotfix restored DLSS and XeSS technologies for supported graphics hardware. The developer also described compatibility checks for AMD frame-generation and latency technologies. Those notes establish that hardware compatibility was part of the demo’s settings work, rather than showing that every upscaler is suitable for every graphics card. The wording about supported hardware matters because the patch concerns compatibility, not a blanket instruction to enable every technology on every machine.
Version 1.03 added more accurate GPU autodetection and continued performance improvements across the demo levels. An automatic hardware selection is a useful starting point, but the patch notes do not turn it into a measured best-settings recommendation. The recorded changes belong to those demo versions and should remain identified by version when comparing older performance reports. That distinction preserves the version history and prevents a demo optimization note from being treated as an independent final-game performance measurement.
Memory and tutorial crash fixes
Version 1.01 was the first published demo hotfix in June. It addressed crashes related to memory management and tutorial screens, alongside places where the player could become stuck in the environment. This is a list of developer-reported fixes for an identified build, so it is more specific than a general promise that a crash can be solved by changing any graphics setting. The developer names the affected systems, allowing an earlier report to be compared with a relevant patch rather than an unrelated troubleshooting suggestion.
The same update improved environmental performance in Chapter I and the General Lothaire encounter. It also adjusted Lantern interactions to make them more consistent across the demo’s two levels. These entries identify which systems received attention, but they do not establish that a later crash with a different message has the same cause. The precise version and feature references help identify the scope of the published fix without promising a repair for an undocumented retail-build error.
Block, level-loading and blood-effects fixes
The version 1.02 demo notes identify crashes caused by excessive player events and by blocking enemy attacks in particular situations. These are distinct symptoms with a published patch reference, rather than one undifferentiated performance issue. A report about the early demo is most useful when its version and triggering action are kept together. The recorded trigger is part of the useful information, because two crashes during the same session need not belong to the same listed issue.
Version 1.03 subsequently fixed a crash while loading the Witch Hunt level and another involving corrupted blood effects. It also mitigated looping audio after certain enemy kills and improved GPU autodetection. The notes support those historical fixes, without supplying a universal repair for the unreleased retail build or a reason to alter game files through an unofficial modification. This is a developer-reported change list for a particular version, and its status should remain attached to the build when citing the fix.
Steam’s game listing and player features
The full Steam game is listed under app ID 2828710 and was still awaiting release at the October 11 check. Its announced date is October 13, 2026, and the page provides a wishlist route before availability. This identifies the full product rather than an archived playtest, a fan download or an old public-demo invitation. The product identity and date are both explicit on the listing, making it a useful anchor when comparing older announcements with current availability.
Steam lists single-player, Steam achievements and Steam Cloud among the game’s features. These belong to the PC storefront entry and should not be used to infer a different platform’s trophy list or subscription terms. The listing also supplies the current minimum requirements, making it the relevant place to distinguish game information from community speculation. A feature label confirms that feature on the Steam entry, while detailed support claims and another platform’s entitlements require their own directly relevant references.
Why the demo differs from the campaign
The public Steam demo used specially adapted versions of Chapters I and VII. In the September development update, the studio explains that these levels were rebuilt for Steam Next Fest rather than simply copied from the finished campaign. Their chapter labels therefore describe the pieces used for the demo, not a complete route through the retail story. The modified structure explains why a guide can discuss a later chapter immediately after an introductory section without documenting the intervening story.
The developer also said that incorporating final-game optimization, balancing and fixes into those bespoke demo levels was not straightforward. This is why the demo’s presentation and difficulty need to be read as a particular build. A video recorded in that version remains useful historical material, but it does not establish the exact state of the game released later. The announcement gives a reason for comparing builds carefully, rather than assuming that an earlier recorded bug or difficulty spike describes every subsequent version.
Sources and further reading
- Valor Mortis — Steam
- Demo Hotfix (Version 1.02) - DLSS is Back!
- Demo Hotfix (Version 1.03)
- Demo Hotfix (Version 1.01)
- The Final Stretch - Development Update
- Valor Mortis Demo is Available Now!