A visible licence agreement is not a Denuvo confirmation
The Steam page asks the player to agree to a third-party end-user licence agreement. This establishes that a licence agreement is attached to the product listing. It does not name Denuvo in the inspected disclosure, so the EULA alone cannot supply an answer about that particular anti-tamper implementation.
The distinction matters because two different forms of information are being read. A licence agreement concerns terms, while a DRM notice identifies a disclosed technology. The collected evidence supports describing what is visible on the page without converting one kind of notice into the other.
Use confirmed PC information for the practical comparison
The current Steam listing does provide hardware requirements and a specific minimum performance target. The demo patch notes separately identify compatibility and stability work on supported graphics technologies. Those are concrete technical details available in the research, unlike an unverified explanation that attributes performance to a particular protection system.
The existence of demo crashes or upscaling changes is not evidence that Denuvo caused them. The developer instead names specific issues in the patch notes, including player events, blocking and blood effects. The sections below retain those documented technical facts without adding a claim about executable protection or its performance cost.
What the Steam disclosure establishes
At the research check, the Steam listing showed a third-party end-user licence agreement. The inspected page did not display a Denuvo or other third-party DRM notice. These are specific observations about the store page, so they support an answer about the visible disclosure without claiming that the executable was independently examined. The visible disclosure is a dated storefront observation, which answers what was shown without replacing an executable check or an explicit developer technology statement.
An end-user licence agreement describes terms, whereas DRM disclosure concerns a different kind of product information. The absence of a visible DRM notice cannot be used as a technical certificate that a game is DRM-free. The developer’s public description also does not establish an anti-tamper implementation, so no affirmative Denuvo claim is added to this guide. That is why the answer stays with the documented listing rather than using a missing notice to make an affirmative technical claim about the released files.
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.
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.
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.
The current release date and the earlier delay
Valor Mortis is scheduled to release on October 13, 2026. The earlier September 24 announcement was changed in a June 11 update, which Gematsu reported with the developer’s explanation. Keeping that sequence in mind resolves the most common disagreement between an older trailer and the current storefronts. The later statement is the one used for current planning, while the earlier announcement remains useful only for understanding the change in schedule.
The October launch announcement continues to use October 13, and the official platform listings support that date. This research was checked on October 11, while the game was still ahead of its full release. It records the announced launch date without substituting a fan-site countdown for a verified global unlock schedule. Release-date confirmation and exact time-zone conversion are separate questions, and only the date has been consistently established across the sources used here.
Sources and further reading
- Valor Mortis — Steam
- Demo Hotfix (Version 1.02) - DLSS is Back!
- Demo Hotfix (Version 1.03)
- Valor Mortis — One More Level
- Launch Trailer and Launch Times
- Valor Mortis delayed to October 13 — Gematsu