RetroArch controller not mapping

Why autoconfig gets it wrong

RetroArch ships an autoconfig database keyed by device name and vendor ID. When it matches, a pad is usable with no setup at all. It fails in three predictable ways:

• Two identical pads report the same ID, so the second one inherits the first one’s profile.
• The pad is a variant the database knows under a different name, so no profile loads.
• The pad has extra inputs — touchpads, back paddles — that no profile covers.

None of these are hardware faults. All of them are fixed by overriding the profile.

Override it by hand

1. Open Settings → Input → Port 1 Controls.
2. Set Device Index to your pad. Cycle through the numbers if the name is ambiguous — each index is a distinct device.
3. Set Device Type to the matching pad class rather than leaving it on “Auto”.
4. Use Set All Controls and press each button in the on-screen order. This is faster and more reliable than binding rows one at a time.
5. Save with Save Core Remap File if you only want it for one system, or Save Game Remap File for one game.

Deal with duplicate devices

If two pads fight over one profile, open the autoconfig folder and remove the profile named after your pad. RetroArch then falls back to manual binding for both, which is preferable to a wrong autoconfig that silently swaps shoulders and triggers.

A tracked case shows the same failure mode with two 8BitDo pads autoconfiguring as one model — the second pad’s inputs land on player one. Binding ports separately is the workaround.

If a specific input never registers

Touchpad clicks and some back paddles report as separate buttons that RetroArch does not expose by default. Enable Settings → Input → Show Unknown Pads so unmapped devices appear in the list, then bind the extra buttons explicitly.

If the overlay shows no response at all for a button, that button is not reaching RetroArch. Test in the OS-level gamepad panel first; if it responds there, the pad is fine and the profile is wrong.