Skip to content
ROB RUN Wiki
ROB RUN WikiMain menu
Language

ROB RUN Controller: Native Support and Mapping Limits

ConfirmedAuthor: KevinUpdated:

Quick Answer

Native ROB RUN controller support is not confirmed in this snapshot. Steam Input can emulate keys and mouse input, but no ROB RUN layout is verified here. For E-0601, connect a physical keyboard and mouse before launch.

Native ROB RUN controller support is not confirmed in the November 12, 2026 snapshot. Steam Input offers controller-to-keyboard and mouse mapping, but that is not proof of native support or a verified ROB RUN layout. If the game displays E-0601, connect a physical keyboard and mouse directly to the PC before launching.

Resolve the ROB RUN input-detection error first

E-0601 means the game did not detect basic keyboard and mouse input devices. It can occur in Remote Desktop or cloud streaming sessions. The documented response is to use a physical keyboard and mouse connected directly to the PC and avoid remote access sessions.

  1. Close the game before changing the input setup.
  2. Connect both physical devices directly to the PC.
  3. Leave the remote access session and launch locally through Steam.
  4. Check whether the same code returns before experimenting with a controller layout.

This error does not prove that controllers will never be supported. It identifies the missing basic input devices in that launch attempt. If it persists with physical devices connected, keep the exact error text and setup details for support.

Treat Steam Input as a mapping experiment

Steam Input’s legacy bindings can translate a controller input into a keyboard key, mouse action, or XInput event. To try a mapping, choose a controller input in the configurator and assign the corresponding input used by the game. Start from the game’s actual keyboard and mouse controls rather than inventing a ROB RUN button layout.

Steam Input legacy binding configurator showing keyboard, mouse, and gamepad input choices

This is Steam’s mapping interface, not a ROB RUN native-controller support screen.

Test one simple input, then check menu navigation and any gameplay action you intend to use. A working button does not establish complete controller coverage. Keep the keyboard and mouse available and stop the experiment if essential controls cannot be reached reliably.

Know what the controller test cannot confirm

The store capture does not list controller support, but an omitted feature is not proof that support is absent. There is no verified controller model list, complete layout, button-prompt set, or controller-only workflow here. Do not buy a particular pad expecting this page to guarantee compatibility. A successful personal mapping remains a setup result, not an official native-support announcement.