Steam scope: Windows PC.
The Mortal Shell II Steam page is the source of truth for the current Windows minimum requirements. Read its CPU, GPU, memory, operating system, storage, and other fields as a support-floor description. Minimum does not mean “guaranteed 60 FPS,” and it does not describe every resolution or graphics preset. A useful check compares each field with the player’s actual machine and keeps performance claims dated.
Confirm the product first
Use base-game AppID 2584270 when checking the requirements. The Open Beta uses AppID 4711740 and can have a different build or workload. If a video cites Beta performance, record that product and date rather than copying its preset into a launch recommendation.
The store title, developer, publisher, release state, and requirements should all match the base product. A similarly named page is not enough. This identity check is especially important when Steam surfaces the Beta as a related download.
Compare every requirement field
Check the operating system before the graphics card. Then compare CPU, GPU, memory, and storage. A machine can exceed the listed GPU while missing memory or storage expectations. Write down the exact component model and driver date; “gaming PC” is not a reproducible specification.
If one field is below the minimum, call it out without predicting a failure. The responsible next step is to wait for a release build or a verified benchmark, not to promise that a single setting will solve the mismatch. If every field is met, the result is still eligibility against the listed floor, not a frame-rate guarantee.
First-launch baseline
Let Steam finish installation and any first-run dependency step. Launch with defaults, reach a menu, and then test a short gameplay scene. Record the resolution, preset, display mode, and whether the issue happens before or after the first load. This baseline is needed before changing an overlay, driver, or graphics option.
If the game stutters only during a first shader pass, record the scene and wait for a repeatable comparison. If it crashes, preserve the error text and save data before trying a destructive workaround. A benchmark without the scene or build date cannot tell a future reader much.
Safe performance notes
Use one repeatable scene, not a menu. Include average behavior and visible stutter or frame-time spikes. If you change an upscaler, shadow setting, or texture option, explain whether image clarity or input feel changed. A performance guide should expose the tradeoff rather than call a preset universally optimal.
If storage is tight, leave room for the installed game, updates, shader caches, and the operating system’s normal temporary space. Do not turn a rough download estimate into a permanent storage promise. For a laptop, record whether the test used wall power and a performance profile, since a battery mode can change the result without any game setting changing.
When a player is below one requirement, the safest advice is to wait for a release-build test or official support response. Avoid registry edits, unofficial DLLs, and save deletion as a first step. A requirement mismatch deserves a measured report, not a risky workaround.
If a problem appears only after an update, capture the update date and compare the same scene again. That gives the Technical page a useful before-and-after record instead of an unscoped claim that the game is simply “broken.”
Keep screenshots and notes together so the result can be checked later.
FAQ
Do minimum requirements guarantee a frame rate?
No. They describe the listed support floor. Resolution, settings, drivers, and scene complexity still determine the result.
Should I use a Beta benchmark for launch?
Only as a separate, dated observation. The Beta is AppID 4711740 and not the full release product.
What should a hardware report include?
Include CPU, GPU, memory, operating system, driver, resolution, preset, build/date, scene, and exact symptom.
Source: the official Mortal Shell II Steam store page; Beta scope is separately listed at AppID 4711740. Checked 2026-08-09.