Mortal Shell II on Steam Deck: check text, prompts and external input
Read Mortal Shell II's current Playable compatibility findings, distinguish handheld from external-controller use, and check readability before a long session.
By Mortal Shell 2 Wiki editorial team · Last updated
Mortal Shell II is listed as Playable on Steam Deck in the compatibility record checked on November 18, 2026. Read the details before choosing your setup: the record flags text legibility, mismatched button prompts and an external controller acting as the primary input. These are meaningful access and control concerns, even if the game starts and a performance check passes.
This page is a compatibility decision guide, not a personally measured preset or a recommendation based on a claimed battery test. Its purpose is to help you distinguish a handheld reading problem, a prompt mismatch and an external-input limitation. General hardware and performance diagnosis belongs in the PC requirements guide.
What the current compatibility record says
Valve’s Playable category means that a game may need some user adjustment. It is different from Verified. The detailed title record is more useful than reading that one badge as a guarantee for every way of playing.
| Report item | Current finding | What to check yourself |
|---|---|---|
| Default controller configuration | Functional | Check the built-in controls and menu navigation before a difficult encounter. |
| Default graphics configuration | Performance check passed | Begin by observing that configuration; this does not publish a frame-rate target. |
| Interface text | Legibility warning | Read item descriptions, menus and ability information on the actual screen you plan to use. |
| Controller glyphs | Mismatch warning | Confirm which physical input each displayed prompt means. |
| External controller as primary input | Not supported finding | Do not assume a docked controller setup is covered by the built-in-controls result. |
These findings describe the published compatibility record, not a new test performed by this site. They do not give an FPS figure, a power limit or a battery duration. A successful default-configuration check also does not establish identical behaviour in every area, every later patch or every custom graphics configuration.
Handheld controls and external controllers are separate checks
Start with the configuration you actually intend to use. Someone holding the Deck and using its built-in controls faces a different question from someone connecting a separate controller to a television setup. The compatibility record’s functional default-layout result does not override its separate external-primary-input finding.
If you already own the game and want to check an external device, establish a known baseline first. Confirm whether the built-in controls navigate the game, then try the external controller in the same menu. Check that it can both select and cancel before entering combat. Record which controller is connected and whether the problem occurs in Steam’s interface, the game’s menus or only during gameplay. That distinction makes a support report more precise.
Do not describe changing an input option or community layout as a guaranteed repair without testing the actual device and build. If a controller does not become the active input, preserve the working configuration instead of repeatedly changing unrelated graphics or save settings. A controller issue is not evidence that the campaign needs to be restarted.
For a purchase decision centred on playing docked with an external pad, treat this finding as relevant to the intended use. A game’s general controller-support description is broader than this particular configuration. Check the current compatibility details again rather than assuming that a desktop controller result or another player’s handheld success answers the same question.
Text legibility is part of being able to play
Small or difficult-to-read text can affect more than comfort. Mortal Shell II asks you to compare equipment and abilities; if you cannot read the information you need to make a choice, that affects how you use those systems. Do not dismiss the warning as merely cosmetic because the scene itself looks clear.
Before a long session, open a menu containing a full description. Can you distinguish the words and the currently selected option at your normal viewing distance? Try another description rather than judging only a large title or a short button label. Check any text or interface options actually exposed by your installed build, and retain a setting only if it improves the information you need to read.
An external display changes viewing conditions but does not prove that the game has passed a different compatibility test. Equally, a screenshot enlarged on a desktop monitor cannot demonstrate comfortable handheld reading. Judge the screen and distance you will use. This page does not promise that changing resolution repairs every text issue or invent an in-game text-size control that may not exist.
Button prompts: separate the icon from the action
A glyph mismatch concerns the picture used to identify an input. Before relying on a prompt in combat, check how that prompt maps to your current controls. Use a safe menu or a low-pressure situation to establish the relationship, then keep the configuration consistent while learning.
There is a useful version distinction here. The developer’s Week 1 update states that Steam Deck and Steam Controller button displays were corrected, along with improved Deck detection. The compatibility record checked for this revision still carries a glyph warning. Report both observations accurately: a documented update and a current compatibility finding can coexist. Neither establishes when Valve will reassess the title or guarantees that the next result will be Verified.
If you encounter an apparent mismatch, note the game version, connected input device and the screen where it appears. A description such as “the menu shows a different button symbol after connecting this controller” is more useful than assuming all inputs are broken. Avoid importing a desktop controller’s button names into an instruction unless you have confirmed the current mapping.
Performance and battery: ask different questions
The default-configuration performance finding is not a benchmark chart. It does not state a measured frame rate, the heaviest encounter or how long the battery lasts. Reviewers’ playtime also cannot supply those answers: time recorded on an account is neither a completion-time study nor a handheld battery measurement.
If you already have access to the game, begin with the current defaults and identify any specific symptom before experimenting. Note whether it occurs during loading, in a dense area or throughout menus and combat. Use the PC troubleshooting checklist for recording the failure. Do not copy a desktop graphics preset merely because the game uses the same name on both devices.
For session planning, use your own device’s observed battery information and a normal stopping point. A published compatibility category does not guarantee a particular duration away from power. This guide supplies no untested frame cap, Proton selection or power-setting recommendation.
Before committing to your setup
- Read the latest compatibility details for the actual game, not an old Beta entry.
- Decide whether built-in handheld controls or an external controller is essential to your plan.
- Check full descriptions and selection indicators for readable text.
- Confirm prompt-to-control mapping before a demanding encounter.
- Keep compatibility findings separate from personal performance and battery measurements.
Use the installation guide to identify the retail listing and the beginner guide for the opening route. The important decision here is whether the recorded limitations fit your intended screen and input setup; the Playable label alone cannot make that decision for you.