No More Room in Hell 2 has native controller support on PC in Armageddon 1.0, and Steam currently labels AppID 292000 with Full Controller Support plus DualShock and DualSense support. Start with one controller connected before launch and Steam’s default per-game input behavior. Confirm the native baseline before adding a community layout, virtual controller, or remapping layer.
Establish one clean input path
Disconnect unused gamepads and disable duplicate virtual-controller or remapper output during the baseline. A physical device plus a translated copy can produce double movement, rapid menu input, or changing prompts.
Test all mission-critical actions
Do more than walk around the main menu. In the Tutorial, test movement, sprint, crouch, camera, aim, firing, reload, quick/strong/charged melee, shove or kick, interaction, carryable handling, inventory wheel, compass, ping or communication access, and pause navigation. Rebind only after confirming the default action works.
Armageddon added rumble and native PC support, while Steam metadata names Full Controller Support. Those labels establish broad operation, not identical glyphs for every third-party controller. Record the hardware model and the prompt family shown when reporting a mismatch.
Use Solo for a longer test because it has zero permadeath. Check inventory immediately after pickup—the 1.0 notes list a short delay before a newly picked item can be used, which is a gameplay known issue rather than necessarily an input failure.
Decide whether Steam Input helps
Native support should be the first baseline. If the device is recognized, prompts are usable, and actions remain stable, avoid adding translation merely because it exists. Steam Input can help an unsupported controller, enable accessibility remapping, or provide a layout, but it can also create duplicate devices or mismatched glyphs when layered over native recognition.
Change the AppID 292000 per-game override only, then relaunch and repeat the same action list. Do not simultaneously change the cable, firmware, layout, and game bindings. If enabled works and default does not, record that. If enabled doubles actions, return to native/default and remove other virtual inputs.
Steam Deck uses its own integrated controls while running the Windows build through SteamOS compatibility. Its official current rating is Playable, not a native Linux or Deck Verified claim. Keep Deck layout results separate from a Windows Xbox, DualShock, DualSense, or generic controller report.
Current launch-week controller issues
Incorrect scheme
Players with hidden Early Access save data could receive the wrong controller scheme. Hotfix #1 was planned to fix this by resetting everyone’s keybindings.
UI focus loss
Controllers can lose focus on elements such as level-up rewards and character creation. Record the screen and preceding action.
Random vibration
Occasional unexplained vibration was under investigation. Compare vibration on and off without changing the rest of the setup.
Sensitivity ceiling
A higher maximum mouse and controller sensitivity was planned for Hotfix #2. Do not claim the new range exists until released notes confirm it.
The August 13 article describes Hotfix #1 as slated for early the following week and Hotfix #2 for the week of August 24. They were planned at the last official check, not live fixes. Preserve custom bindings outside the game only through documented Steam features, and expect a future official reset if the announced change ships.
Fix common symptoms methodically
For no input, confirm the controller works in Steam, relaunch with it connected, try another port or cable, and remove duplicate devices. For double input, disable one translation/remapper layer. For wrong prompts with correct actions, compare native and one Steam Input state; glyph mismatch is separate from control failure.
For menu focus loss, use mouse or keyboard temporarily only where safe, capture the exact screen, and avoid deploying until the selected Responder and loadout are confirmed. For a binding that will not change, note that the Unload keybind was under investigation specifically; do not reset every file before checking whether the symptom is that known binding.
For input lag, compare Tutorial or Solo with stable performance. Low or uneven frame rate, display processing, wireless interference, and online latency can all feel like controller delay. A wired comparison removes battery and radio variables, but it does not prove every wireless setup is poor.
Remap around mission priorities
Keep movement, camera, primary combat, shove or kick, interaction, and quick inventory access reachable without hand conflict. Actions needed while carrying or reviving matter more than a visually symmetrical layout. Preserve a way to communicate or ping because infection, carryables, and extraction require fast team information.
After remapping, repeat a complete Tutorial segment and restart once to ensure settings persist. Record whether the layout is stored through Steam Input or the game so another layer does not overwrite it later.
Report an actionable input bug
Include controller model, wired or wireless method, Windows version, Steam Input state, game bindings, game version, exact menu or mission, expected action, actual action, and whether keyboard/mouse works. For focus loss, include the path used to reach the element. For vibration, include the scene and preceding event.
Use Steam Deck for integrated Deck controls, Crash Fixes when the process terminates, and Updates to verify whether a planned keybinding or sensitivity fix has actually released.