pcsx2 not detecting controller

PCSX2 PCSX2 latest stable / Windows 10, Windows 11, Linux Last verified October 2026 Risk: none
Quick answer

Reset the controller binding in PCSX2 and restart the emulator. Detection failures usually come from a stale mapping or a pad not re-scanned.

PCSX2 doesn’t see your gamepad, or it sees it but buttons do nothing. The question shows up as “PCSX2 not detecting controller”, “PCSX2 not detecting Xbox controller”, and “PCSX2 controller not working” — all the same root: PCSX2 reads gamepads through an SDL mapping that didn’t refresh.

Fix the mapping first

  1. Open Settings → Controllers and re-bind
    Pick the device in the dropdown and walk through the bind buttons again. Even if the pad appears listed, a mapping that wasn't refreshed after a driver or Windows update leaves every button dead.
    Pressing a bound button lights up the matching input in the mapper.
  2. Restart PCSX2
    SDL rescans gamepads at launch. A pad connected after PCSX2 started, or one that Windows only half-detected, shows up correctly after a restart.
    The controller dropdown lists the pad with a recognised name.
  3. Confirm Windows sees it first
    Check Devices & Printers or Game Controllers in Windows. If Windows doesn't list it, PCSX2 never will — fix the Bluetooth or USB connection there before blaming the emulator.
    Windows lists the controller as connected and working.

Xbox and Xbox-like pads

  1. Use the Xbox Wireless Dongle or a cable
    Bluetooth works but some pads — including third-party Xbox-style controllers — report incorrectly when already powered on, so the emulator grabs the wrong device. A wired or dongle connection is the reliable path.
    The pad binds every button without dropouts.

If it still won’t bind

Controller drift or phantom input is a different problem — see the Xbox controller connected but not working page for driver and firmware steps. General emulator input on Steam Deck is covered separately.

Sources pcsx2.net · github.com
Last verifiedOctober 2026
CorrectionsSpotted an error? See our editorial guidelines