PCSX2 controller not working
A PS2 controller stops responding in PCSX2 when the pad isn't bound. Open Pad settings, select your device, then map each button.
Check the port before the pad
PCSX2 gives every controller a physical port, exactly like the console did. A pad that works everywhere else but does nothing in PCSX2 is usually sitting on Port 2 while the game expects Port 1 — or the port is set to “None” after a config reset.
Open Config → Controllers → Pad and look at the four port slots. Each should name a device type (DualShock 2 for most games) and an API. An empty slot with “None” is the whole problem.
Pick the right input API
The API dropdown decides which layer reads your pad, and choosing wrong produces partial input — some buttons work, triggers or sticks don’t.
| API | Good for | Notes |
|---|---|---|
| SDL | Most modern pads, DualSense, Switch Pro | Handles hot-plug and vibration best |
| XInput | Xbox pads | Fixed layout, no remapping of triggers |
| DInput | Older pads and adapters | Often misses analog triggers |
If a pad binds but the left stick moves the camera and the right stick does nothing, the axes were bound to the wrong entries — rebind rather than swapping the device.
Bind each control by hand
- Select Port 1, set device type to DualShock 2.
- Choose the API, then press a button on the pad so PCSX2 picks the device index.
- Click a button row, press the matching control, and move on. Do the sticks last — PCSX2 waits for the axis to cross its range.
- Set Large Motor and Small Motor to the same device so vibration actually fires.
- Save, then reboot the game rather than reloading a state.
Known quirks that aren’t your fault
The tracker carries a few real input bugs worth recognising: a stick that glitches when two axes share one binding, pads already powered on before launch not being detected, and vibration failing through certain USB adapters. Reconnecting the pad after PCSX2 has started, and rebinding one axis per direction, works around all three.