Mortal Shell II Controller Not Working — Detection, RT and Vibration

FIRST CHECK

Mortal Shell II officially supports controllers; first identify whether the whole pad is missing, one trigger fails, bindings conflict, or only vibration is absent.

First identify which failure you have: no controller input at all, one trigger that will not fire, conflicting rebound actions, or missing vibration. Mortal Shell II's current Steam data lists full controller support plus DualShock and DualSense categories. A dead RT button and absent haptics therefore need different fixes from a controller that Steam or the game cannot see.

Choose the matching symptom

What happens	Start here	Do not assume
Steam does not see the controller	Connection, firmware, cable or Windows device state	that Mortal Shell II is the cause
Steam sees it, but the game does not	Launch through Steam and try one Steam Input override	that deleting saves is necessary
Movement works, but RT will not shoot	In-game binding, duplicate action and trigger layout	that the whole controller is unsupported
A rebound button performs two actions	Clear the old assignment and rebuild one binding	that the new binding replaced the old one
Inputs work, but there is no vibration	Force Feedback and device-specific haptics branch	that the pad is not detected

If the whole controller is missing

1. Connect the controller before launching the game.
2. Open Steam → Settings → Controller and confirm the device responds.
3. Launch Mortal Shell II from the Steam library, not directly from the executable.
4. Open Properties → Controller and write down the current Steam Input override before changing it.
5. Try the default state, then one alternate state; fully restart the game between attempts.
6. Disconnect extra physical pads, virtual controllers and remapping tools for one clean launch.
7. Verify the game files if Steam detects the pad but a clean launch still does not.

A developer response during the Beta confirmed Xbox-controller support and asked players to verify that Steam recognized the device. That is still a useful first split, but it is not evidence that every launch issue has the same cause. Change only one Steam Input state at a time, then restore the original if the attempt fails.

If RT works in menus but will not shoot

This is an action-input problem. Current launch reports include players whose controller otherwise worked while the fire action did not. A developer said the report was logged; another developer reply recommended restarting and verifying files while asking for the exact controller model.

Use this order:

1. Open the full game's controller bindings and confirm Fire has one intended input.
2. Check whether another action is still assigned to RT after rebinding.
3. Reset just the conflicting binding before rebuilding a custom layout.
4. In Steam's controller layout, inspect the RT full-pull action.
5. If the current layout uses a hair-trigger or unusual threshold, try a standard trigger profile.
6. Restart Mortal Shell II and try Fire before changing another value.

One launch player reported success after changing Steam Input from a hair-trigger layout to a standard trigger and lowering the dead-zone threshold. That is a device-specific report, not a universal number to copy. The reusable lesson is to make sure the game receives a full-pull event.

If rebinding triggers two actions

The developer confirmed that the full game supports controller rebinding. A current player report says a newly assigned R2 action can coexist with the old action and trigger both. If that happens, remove the old assignment explicitly rather than assuming the new selection replaced it.

Try the changed control in an empty or safe area. If the in-game menu cannot clear the conflict, Steam Input can temporarily map the controller button to the keyboard command for the one intended action. Keep a note of this workaround so it can be removed after an update.

If only vibration or haptics are missing

Do not keep cycling detection settings when movement and buttons already work. Confirm Force Feedback is enabled, then compare a repeatable event such as a light attack, block, incoming hit or ranged shot. Current launch reports disagree: some DualSense users report normal vibration and adaptive-trigger behavior, while others report little or no feedback on PC or PS5.

That disagreement means there is no single verified launch-wide fix. Include the controller model, wired or wireless connection, platform, Steam Input state and affected actions in a report. Missing vibration is a feature-quality issue; it should not be merged with “controller not detected.”

What to include in a useful bug report

If the problem remains, submit the controller model, wired or wireless state, Steam Input setting, operating system, current game build, whether another Steam game detects it, and the exact failing action. State whether the issue is detection, RT/full-pull, duplicate bindings or vibration. A precise report is more useful than “controller broken” and makes it easier to remove temporary workarounds later.

Avoid deleting configuration or save files as an opening step. None of the current developer replies used here asks players to erase progression, and the safer checks above are reversible.

Return to the Mortal Shell II guide hub or review the system requirements before changing graphics or runtime settings.

Sources

• Official Mortal Shell II Steam listing and controller categories
• Developer reply on controller detection — Beta evidence
• Developer confirmation of full-game rebinding and trigger troubleshooting
• Developer-acknowledged launch input report
• Current launch vibration reports
• Current duplicate-binding report