Log in

RetroArch doesn't detect my controller — no input in games

High3 solutions

If RetroArch won't detect your controller, it's almost always the input layer — not a broken pad: the wrong input driver, a missing autoconfig profile, another app such as Steam Input claiming the controller, or a pad that's bound in the menu but never assigned to a player port. Fix those in order and the gamepad comes back — the steps below cover each cause.

You plug a controller into RetroArch and nothing happens: the gamepad isn't listed, you can't navigate the menu with it, or — the confusing one — the menu responds but the actual game gets no input. Sometimes it works after a reboot and then stops; sometimes only player 1 is recognised and a second pad is dead.

Cause: RetroArch doesn't read your controller directly. It relies on an input driver (the layer that talks to Windows/Linux) plus a controller autoconfig profile (a small file that maps your specific pad's buttons to RetroArch's virtual layout). When a pad isn't detected it's almost always one of: the wrong input driver for your OS, a missing or mismatched autoconfig profile, the pad being claimed by Steam Input or another remapper, or the controller being bound in the menu but not assigned to a player port for the core.

None of this is a broken install — the same RetroArch that fails to see your pad will work perfectly once the driver and profile line up. The fixes below go in order of how often they're the culprit.

Last updated 1 week ago0 users reported this issue29
Sign in to interact

Solutions

solution #1302

set-the-right-input-driver-and-update-profiles (sortOrder=1, isMostHelpful)

Pick the correct input driver and download the controller profiles. This fixes the large majority of "not detected" cases.

  1. Open RetroArch and go to Settings → Drivers → Input. On Windows, try xinput first (best for Xbox-style pads). If your controller is a DirectInput device (many generic/PS-style pads), switch to dinput. On Linux, use udev. Change the driver, then fully restart RetroArch — input driver changes only take effect after a restart.
  2. Update the autoconfig profiles: Main Menu → Online Updater → Update Controller Profiles. This downloads the latest mappings for hundreds of pads so RetroArch can recognise yours by name.
  3. Reconnect the controller. Go to Settings → Input → Port 1 Controls (or watch the on-screen notification) — if autoconfig worked you'll see your pad's name and a "configured" message.

Wired vs wireless tip: test with a USB cable first. Bluetooth pairing issues masquerade as "RetroArch can't see the controller" when the OS itself hasn't connected it. Confirm Windows/Linux sees the pad in its own settings before blaming RetroArch.

Jul 30, 2026
Was this helpful?0

solution #1303

stop-steam-input-or-another-app-grabbing-the-pad (sortOrder=2)

The OS sees the controller but RetroArch still gets nothing? Another program is intercepting it. The most common culprit is Steam Input, which can capture the pad system-wide and hand RetroArch a fake "virtual" controller (or nothing).

  1. If you launch RetroArch through Steam: right-click it in your Library → Properties → Controller → set to Disable Steam Input.
  2. If you launch RetroArch standalone but Steam is running: open Steam → Settings → Controller and turn off desktop/global Steam Input, or close Steam entirely and relaunch RetroArch to test.
  3. Close other remappers (DS4Windows, x360ce, JoyToKey, vendor software). Two layers mapping the same pad cancel each other out. Use either a remapper or RetroArch's native input — not both at once.

After freeing the pad, go back to S1 and let autoconfig run again.

Jul 30, 2026
Was this helpful?0

solution #1304

assign-the-pad-to-a-port-and-rebind-manually (sortOrder=3)

Menu works but the game has no input — or your pad has no autoconfig profile. This means the controller isn't bound to the player port the core reads, or the mapping is missing.

  1. Assign the port: Settings → Input → Port 1 Controls → Device Index — make sure it points at your actual controller (not "Disabled" or a phantom device). For a second player, set Port 2 Controls the same way.
  2. Manual rebind (no profile exists): in Port 1 Controls choose Set All Controls and press each button as prompted. This builds a working map even for unknown pads.
  3. Save it so it sticks: still in Port 1 Controls, choose Save Controller Profile — RetroArch writes an autoconfig file named after your pad, so it's recognised automatically next time.
  4. Still dead in-game only? Open the in-game menu (F1) → Controls and confirm the core's User 1 Device Type is a normal gamepad, and that no per-game remap is overriding everything to "unbound".

If a single pad works in the menu and in one core but not another, the issue is core-specific device type (step 4), not detection — RetroArch can see the controller fine.

Jul 30, 2026
Was this helpful?0
Experiencing a different problem?Report a new issue to help the community find solutions.

Comments (0)

No other comments yet. Be the first to share your thoughts.

Sign in to_leave_comment

On This Page