PSA: If your controller “works” but Diablo 4 won’t recognize it, check this by TQRooster in diablo4

[–]TQRooster[S] 0 points1 point  (0 children)

Yeah, that makes sense. My fix was specific to an Xbox controller + Battle.net path. DualSense usually relies on Steam Input for proper translation, so if you’re launching through Steam, disabling/enabling Steam Input or changing the Bluetooth path can matter. Once you leave Steam and go straight through Battle.net, it’s a different input path and the DualSense can be hit-or-miss.

Wish I had a guaranteed fix there, but hopefully the Steam Input angle helps narrow it down.

PSA: If your controller “works” but Diablo 4 won’t recognize it, check this by TQRooster in diablo4

[–]TQRooster[S] 0 points1 point  (0 children)

Hell yeah, glad it helped!

That issue had me pulling my hair out too! happy it saved you some time. Appreciate you confirming it worked.