Skip to content
Dusk Guide

Controller not detected

Controller not detected

Most 'no controller' issues come from a layer collision — Steam Input intercepting events Dusk expects to handle directly, or a Bluetooth pairing that's listed but not active.

UPDATED 2026-05-104 minBeginner

No ROMs / no copyrighted assets

This independent guide does not host or link to game files. Use your own legally obtained copy.

Symptoms

  • Dusk shows keyboard prompts but ignores controller input.
  • Controller is paired in OS but inactive in Dusk.
  • Sticks register but buttons don't, or vice versa.

Likely causes

  • Steam Input is intercepting events.
  • Wrong driver layer (XInput / DirectInput / SDL).
  • Bluetooth pairing is stale.
  • Wired connection charges only — needs a data cable.

First safe fixes

Try in this order

  • Disable Steam Input for Dusk and relaunch.
  • Re-pair the controller fresh over Bluetooth.
  • Try a known-good wired connection with a data cable.
  • Test the controller in another app to confirm it's seen by the OS.

Platform-specific notes

  • Steam Deck: Right-click → Properties → Controller → set to 'Disable Steam Input'.
  • Windows: Update Xbox Accessories / DS4Windows; reboot if controller was just paired.
  • Android: Forget and re-pair the Bluetooth controller, then relaunch Dusk.

Still stuck?

Open the troubleshooting wizard for a different symptom or platform combination. If everything checks out and the issue persists, file a bug at the official Dusk project.

Reference slug: controller-not-detected

Related guides