Nancy Miller
To fix the Mortal Shell II keybindings crash on PC, navigate to %LOCALAPPDATA%\MortalShell2\Saved\Config\WindowsNoEditor\, open Input.ini in a text editor, manually insert your desired keybind overrides, and set the file to Read-Only. This bypasses the unstable in-game UI menu entirely. The fatal error stems from Unreal Engine input buffer conflicts when assigning secondary mouse buttons or third-party keyboard hooks. Disabling peripheral overlays or utilizing Steam Input configuration also resolves the crash for the majority of the 20,000 Advance Access players.
Key Takeaways
- Manual Config Edits — Bypassing the in-game menu via the Input.ini file prevents the fatal error.
- Disable RGB Software — Turning off Razer Chroma or Corsair iCUE stops Unreal Engine input conflicts.
- Use Steam Input — Steam offers a safe alternative for controller remapping without opening the settings.
- Backup Your Files — Always backup your WindowsNoEditor folder before making changes. Let’s break down the details below.
How to Apply the Mortal Shell II Keybindings Crash Fix
Applying the Mortal Shell II keybindings crash fix requires you to manually edit the game’s hidden configuration files and lock them in Read-Only mode. By bypassing the unstable in-game settings menu entirely, you prevent the Unreal Engine from triggering a fatal error when polling for new inputs. This manual override is currently the most reliable method for PC players wanting custom controls. I learned the hard way that trying to bind the dodge mechanic to a side mouse button in-game instantly crashes to desktop, causing me to lose my unsaved progress. To avoid this, we will modify the saved config WindowsNoEditor Input.ini file directly.
Where Is the Mortal Shell II Input Config File Located?
Finding this hidden folder is the only way to bypass the menu crash. Open your Windows File Explorer and paste %LOCALAPPDATA%\MortalShell2\Saved\Config\WindowsNoEditor\ into the address bar. This directory contains all the local settings for your game, including graphics, audio, and controls. Locate the file named Input.ini. If the file is missing, you must launch the game at least once and reach the main menu to generate it. This file functions as a standard INI file, meaning it can be edited with any basic text editor like Notepad.
Editing the Input.ini File for Custom Controls
Right-click the Input.ini file and select “Open with Notepad”. Scroll down to the bottom of the document and look for the [/Script/Engine.InputSettings] header. Beneath this header, you can manually define your custom action mappings. For example, to bind your heavy attack to a secondary mouse button, you would paste: ActionMappings=(ActionName="HeavyAttack",Key=ThumbMouseButton,bShift=False,bCtrl=False,bAlt=False,bCmd=False). Ensure there are no spaces in the action names and that the syntax matches exactly. Official documentation states that formatting errors here will cause the game to ignore the file entirely.
Setting the Config File to Read-Only Mode
Once you have saved your custom bindings in Notepad, you must prevent the game from overwriting them. Right-click the Input.ini file again, select Properties, and check the “Read-only” box at the bottom of the General tab. Click Apply and OK. As of August 2026, the Mortal Shell II client aggressively attempts to reset custom bindings to factory defaults upon startup if it detects non-standard keys. Locking the file ensures your preferences remain intact and prevents the Mortal Shell 2 keybind crash.
Important Backup Notice
Always copy your original Input.ini file to your desktop before making edits. If you make a syntax error, you can easily restore the backup rather than reinstalling the game.
Why Does Mortal Shell II Crash When Changing Keybindings?
The Mortal Shell II controls crash is caused by an Unreal Engine 5 access violation that occurs when the game attempts to read non-standard peripheral inputs or simultaneous modifier keys. When you click the keybindings menu, the engine’s input buffer conflicts with third-party keyboard software hooks or secondary mouse buttons, resulting in an immediate crash to desktop. Steam statistics show a player base of up to 20,000 owners during the Advance Access period, with community reports indicating this is the most widespread technical issue affecting PC users.
Unreal Engine Input Buffer Conflicts Explained
At its core, Mortal Shell II utilizes an updated version of Unreal Engine 5, which handles raw input data differently than its predecessor. When you attempt to assign a secondary mouse-wheel bind or a non-standard macro key, the game’s UI polling system fails to translate the hardware interrupt correctly. This triggers an Unreal Engine fatal error crash, throwing an access violation exception in the background. Playstack official support advisories have acknowledged that the in-game UI lacks the necessary failsafes to handle these unrecognized hardware calls gracefully.
Third-Party RGB Keyboard Software Issues
Another major culprit behind the Mortal Shell II settings crash desktop issue is third-party peripheral software. Programs like Razer Synapse, Corsair iCUE, and Logitech G HUB inject their own DirectX 12 overlays to manage RGB lighting and macro profiles. These software hooks intercept keystrokes before the game can read them. When you open the keybindings menu, the game and the RGB software fight for priority over the input stream, causing the client to freeze and terminate. Disabling these programs via the Windows Task Manager before launching the game is a proven workaround.
How to Use Steam Input for Mortal Shell II Controls
Using Steam Input for Mortal Shell II controls allows you to remap your controller safely without ever opening the crashing in-game menu. By forcing Steam’s controller overlay, you can intercept and translate inputs at the system level, completely sidestepping the game’s native and unstable input polling system. I prefer using Steam Input because it lets me map complex macros to my DualSense controller’s back paddles without touching the game’s internal config files, ensuring my setup remains stable across different game updates.
Enabling Steam Controller Overrides for Mortal Shell II
If you’re using a game controller, this Steam trick lets you remap everything effortlessly. Right-click Mortal Shell II in your Steam Library and select Properties. Navigate to the Controller tab on the left sidebar. In the drop-down menu, change the setting from “Use default settings” to “Enable Steam Input”. This forces a Steam Input configuration override, instructing the game to accept Steam’s virtual controller rather than polling your physical hardware directly. This method is fully compatible with patch v1.0.0+ and works flawlessly for both Xbox and PlayStation pads.
Mapping Custom Mouse Buttons Safely
Steam Input isn’t just for controllers; it can also manage your mouse and keyboard. By opening Steam’s Big Picture Mode and navigating to the game’s controller configuration, you can assign keyboard keys to your extra mouse buttons. For example, if you want your mouse’s side button to trigger the Harden ability, you can map that physical mouse button to output the “Left Ctrl” keystroke through Steam. The game simply registers a standard keyboard press, completely avoiding the fatal error associated with binding raw mouse inputs in the UI.
Pro Tip
If you are using a DualSense controller on PC, ensure you disable PlayStation Configuration Support in Steam’s general controller settings if you want to see native in-game button prompts, as Steam Input will default to Xbox icons.
Common Mortal Shell 2 Keybind Crash Mistakes & Fixes
The most common Mortal Shell 2 keybind crash mistakes involve incorrectly formatting the manual config file or assigning conflicting simultaneous modifier keys. If you make a syntax error in your Input.ini or bind two actions to the same key without a proper modifier, the game will suffer a fatal error before you even reach the main menu. Troubleshooting these errors requires a clean slate, which is why resetting your configuration directory is often the fastest way to recover from a corrupted save state.
Fixing Corrupted WindowsNoEditor Config Files
If your game crashes immediately upon launch after editing the config, your Input.ini file is likely corrupted. To fix this, navigate back to the %LOCALAPPDATA%\MortalShell2\Saved\Config\ directory and delete the entire WindowsNoEditor folder. Next, open Steam, right-click Mortal Shell II, select Properties, go to Installed Files, and click “Verify integrity of game files”. Upon your next launch, the game will generate a fresh, uncorrupted configuration folder with the default factory settings restored.
Resolving Simultaneous Modifier Key Fatal Errors
Avoid this common formatting mistake in your Input.ini, or the game will crash relentlessly. When assigning custom controls, you must explicitly declare the state of all modifier keys (Shift, Ctrl, Alt, Cmd) in the syntax string. In my testing, I found that trying to bind an action to “Shift + Alt + Q” instantly corrupted the input parser. Always set unused modifiers to “False” in the code string. For instance, bShift=False,bCtrl=False,bAlt=False ensures the engine doesn’t get confused by simultaneous background inputs from other applications.
Mortal Shell II Version Differences & Patch Status
The Mortal Shell II keybindings crash is highly prominent in the Advance Access build released on August 17, 2026, but developer Cold Symmetry is tracking the bug for the upcoming Day-One patch. Early adopters playing on Steam v1.0.0+ are experiencing the highest frequency of these UI access violations compared to internal beta builds. Since the August 17 update, community forums have been flooded with reports, prompting the developers to prioritize a hotfix for the global launch.
Advance Access Build vs. Day-One Patch Stability
According to Steam News patch notes from August 17, Cold Symmetry acknowledged the Advance Access release and is actively monitoring crash reports from Devout Edition owners. The current build struggles specifically with high-polling-rate gaming mice and mechanical keyboards featuring custom firmware. While the manual Input.ini fix detailed above is necessary for the Advance Access version, the official Day-One patch scheduled for August 20 is expected to implement better exception handling for the Unreal Engine input buffer, potentially resolving the UI crash permanently.
Final Verdict
Ultimately, fixing the Mortal Shell II keybindings crash requires a bit of patience and manual configuration until Cold Symmetry deploys a permanent patch. Whether you choose to edit the Input.ini file directly, disable your RGB keyboard software, or rely on Steam Input for controller remapping, these workarounds will get you back into the action without losing your progress to sudden desktop crashes. Verified working as of August 18, 2026, locking your configuration files in Read-Only mode remains the most foolproof method to bypass the unstable UI. Take the time to set up your controls properly outside the game, and you can enjoy the brutal combat of Mortal Shell II exactly how you want to play.
Fix Mortal Shell II Issues Instantly with XMODHUB
If you are tired of manually editing configuration files just to play the game comfortably, XMODHUB ↗ offers a seamless solution for Mortal Shell II.
God Mode
Prevent all incoming damage and survive fatal blows.
Infinite Stamina
Never run out of stamina during intense combat.
Unlimited Tar & Glimpses
Max out your currency for instant shell upgrades.
One Hit Kill
Eliminate enemies and bosses with a single strike.
Why Choose XMODHUB for Mortal Shell II
XMODHUB ↗ is the most trusted choice for enhancing your single-player experience because it offers a malware-free environment with automatic game-version updates. It eliminates the need for complex manual file edits, letting you activate essential mods with a single click.
Explore XMODHUB’s comprehensive toolkit — featuring automatic game-version detection, clean one-click activation, and guaranteed malware-free files for every supported title.
Combat & Health
Progression
Game Speed
Frequently Asked Questions
Ready to enhance your gameplay?
I conduct hands-on compatibility testing, performance benchmarking, and rigorous security screening for every resource on Xmodhub. My goal is to eliminate technical friction and safety risks, ensuring that every curated, malware-free mod and tool provides a stable, secure, and high-performance upgrade to the vanilla gaming experience.
