Mortal Shell II Camera, Controller and Target Steering Settings
Published 2026-08-22 · Updated 2026-08-22
Configure target steering, lock-on, sprint camera shake, rumble and controller behavior using options documented in official Mortal Shell II patch notes.
Sources
Checked on 2026-08-22. Store details and balance may change after patches.
Separate four different control problems
Aiming complaints often combine facing, camera motion, lock-on, and physical controller feedback. Official patches document separate controls for target steering, sprint camera shake, and rumble, plus a fix that allows lock-on toggling during attacks. Diagnose them separately. Write down what actually fails: the character rotates toward an unintended enemy, the camera motion is uncomfortable, lock-on cannot be changed at the desired moment, or vibration is unwanted. Starting with a precise symptom prevents a player from disabling every assistance option and losing the specific behavior that was helping.
Start with Default target steering
Patch 86845 recommends Default for most players. During some attacks it rotates the character toward enemies according to distance and angle. Use a familiar single enemy, stand at a repeatable angle, and perform the same attack several times. If facing becomes more consistent, keep Default while testing the rest of the setup. Target steering is not the same as lock-on and does not promise that every attack will redirect. Avoid changing sensitivity or camera distance during this test because that makes the result difficult to attribute.
Use Light when you want a narrower assist
The official note describes Light as using a narrower angle and recommends it for experienced players who want more control. It is a reasonable second test when Default pulls attacks more strongly than desired. Repeat the same enemy, spacing, weapon, and attack used for Default. Choose the option based on directional consistency, not on claims that one mode deals more damage. The developer does not state a damage bonus, faster animation, or larger posture effect for any steering setting. This is an input-behavior choice.
Treat Off as a diagnostic setting
Off completely disables target steering and the official notes do not recommend it. It can still isolate whether assistance is causing an unexpected turn. Test briefly in a controlled encounter, then compare the result with Light. If manual facing causes more misses, restore assistance. Do not publish or follow a blanket instruction that skilled players must use Off. The useful outcome is a stable personal setting with a reproducible reason. Record it in the Build Planner notes if directional behavior is central to how a weapon or Shell setup is tested.
Retest lock-on after Patch 86845
The same patch fixed an issue that prevented players from toggling lock-on during attacks. If an older guide tells players they must wait for an attack to end before changing the target, verify that instruction on the current client. Practice toggling during a low-risk sequence and note whether the intended target changes without disrupting movement. The patch note establishes that the restriction was a bug, but it does not prescribe a universal lock-on strategy. In groups, manual camera control and lock-on each have tradeoffs that depend on spacing and visibility.
Reduce sprint camera shake for readability
Patch 86845 introduced a slider for camera shake while sprinting. Lower it when travel causes discomfort, when environmental detail becomes difficult to read, or when route landmarks blur during fast movement. Then repeat the same short route and stop at the same landmark. A comfort improvement is a valid outcome even if frame rate is unchanged. Camera shake is a presentation effect; changing it should not be advertised as a GPU optimization unless an authoritative measurement proves that. Keep graphics settings constant while deciding whether the motion level is comfortable.
Disable rumble or force feedback when needed
Patch 86328 added an option to disable rumble and force feedback. Turn it off for accessibility, preference, battery use, or to isolate unexpected vibration. Confirm the selected value, reconnect the controller if necessary, and repeat one action that normally triggers feedback. The official source does not connect rumble to crashes, latency, or frame drops, so do not use this switch as a generic performance recommendation. If feedback returns after a restart, report the controller model, wired or wireless connection, platform, patch, and whether Steam Input is involved.
Save a reproducible settings baseline
Once each control behaves predictably, record target steering mode, camera shake value, rumble choice, input device, connection type, and current patch. Capture screenshots of the option pages without account details. Retest after an official update that mentions controls, camera, targeting, or input. Change one variable at a time and keep a short familiar combat route as the benchmark. This baseline solves two problems: it restores a comfortable configuration after resets and gives a bug report enough context to distinguish a game regression from a controller profile, platform overlay, or personal preference.