I’ve had this issue before on an xbox controller, and the solution was to use wired connection. That solved it, but it’s far from an ideal solution. Now I use my Steam Controller (2026) with the wireless dongle, and again I keep getting consistent disconnects when using the controller.
I’ve tried the following things so far:
- Already did /console GamePadEnable 1
- Launched WoW.exe (and WoWClassic.exe) directly from steam
- Disabled Steam overlay
- Used wired connection, still disconnects
The issue persists through these fixes and it’s clearly an issue on Blizzard’s end, because no other game seems to suffer from this issue, not even Lord of the Rings Online which doesn’t even natively support controllers.
It’s as if Blizzard servers don’t mesh well with the controllers and casually decide to not register any of my characters movements, consider me AFK and boot me off the server. This happens most of the time after 15 minutes the first session, then the second session it’s more like 5 minutes and the third, if I even have the energy to try again, is even less.
For anyone wondering, I’m using controller to play mainly on World of Warcraft Classic Anniversary, it’s very enjoyable to sit back and play the game this way.
The weird part about this situation is that it worked fine for a couple of months. My steam controller arrived around mid-may, and has been working fine wirelessly for some time, until the last patch of TBC Anniversary hit.
This is probably the cause of Blizzard’s spaghetti code, but I’m hoping someone else here found a solution to this issue.