---
title: "PPSSPP controller not detected — configure XInput or DirectInput gamepad in settings"
canonical_url: https://emudesk.com/issues/ppsspp-controller-not-detected-gamepad-fix
content_locale: en
source_locale: en
entity_type: issue
index_status: index
published_at: 2026-08-31T18:22:23.000Z
updated_at: 2026-09-01T00:45:02.732Z
freshness_status: fresh
---

# PPSSPP controller not detected — configure XInput or DirectInput gamepad in settings

PPSSPP can use virtually any USB or Bluetooth gamepad, but it won't auto-configure many controllers — especially PlayStation DualShock/DualSense pads on Windows — without a small setup step.

Symptoms of controller detection failure in PPSSPP:

  Controller shows up in Windows Device Manager and works in other games, but PPSSPP ignores all button presses
  PPSSPP opens its controller mapping screen but pressing buttons on the gamepad registers nothing
  Only some buttons respond (e.g., the analog stick moves but face buttons are dead)
  Xbox controller works fine but a PS4/PS5 DualSense does not, or vice-versa


Why this happens: Windows exposes gamepads through two APIs — XInput (modern, preferred by Xbox-style controllers) and DirectInput (older, used by most generic and PlayStation controllers). PPSSPP defaults to XInput mode. An Xbox controller works immediately in this mode; a DualShock 4 or DualSense connected without a translation layer is presented as a DirectInput device and PPSSPP simply won't see it in XInput mode. Switching the input mode — or using a bridging tool like DS4Windows — closes the gap.