XInput Controlls broken after a few days

[Dandeloreon]

ISSUE
Steam Gamepad Controls Completely locks up Controller Number 1.

OS: Windows 10

Reproduction Steps:

• Make sure a wired X-input style controller is plugged in. I have experienced this with various gamepads ranging from a Thrustmaster GPX gamepad (xbox 360 model) to 8Bitdo SN30/SN30Pro+ to Official Xbox One controllers.
  
• Power on computer
  
• Login to windows
  
• Start Steam
  
• Select LIBRARY from the main menu
  
• Select ALL GAMES
  
• Launch any controller enabled game. A short list of games that can trigger the problem are as follows...
  
  • Boomerang Fu
    
  • Evoland: Legendary Edition
    
  • Hotshot Racing
    
  • Monster Hunter: World
    
  • No Man's Sky
    
  • Stardew Valley
    
  • Warframe
• Play your selected game for a while using controller.
  
• exit game
  
• Make sure windows power management is set to turn the PC Screen off. I currently use a 15 minute timer here.
  
• Make sure windows power management is set have the pc go to sleep. I have mine set to 3 hours, but the default is usually after 30 minutes or so.
  
• Begin loop of events
  
  • Do not physically disconnect controller. My Controller is left plugged in at all times.
    
  • Leave Computer overnight
    
  • Wake up the computer
    
  • login
    
  • start another game from the above list.
    
  • play above game with controller
    
  • exit game
    
  • repeat loop for a few days.
  
  RESULTS
  The Controller input for the only controller connected to the system during this time will break. The game acknowledges the controller but that is about it. When I try to actually use the controller for inputting commands into the game everything is ignored. Also, Disconnecting and reconnecting the controller while the game is still running fails to resolve the problem.
  
  EXPECTED
  To be able to control the games using a controller.
  
  Note: I am able to produce this issue after a few days. My computer has been up for less than 7 days and controller input has broken at least 3 times already. The only fix is to restart steam, but this is not an acceptable fix since steam should not be causing this bug.

[austinp_valve]

From your logs it looks like you're using the extended features driver for Xbox controllers. Does this still happen with the driver uninstalled?

[Dandeloreon]

I will try disabling the extended features driver and see if that helps. I do remember that this bug has been happening for more than a year now. This bug causes some really bad behavior on gamepads. As an example of some of how the gamepad behaves...

• connect controller to pc that is off.
  
• Start Computer - Gamepad will start off as gamepad 1
  
• login to pc and start steam.
  
• play any steam game that has full controller support.
  
• exit game
  
• leave PC over night. The power management will put the pc to sleep, and turn off the monitor.
  
• The Loop:
  • wake up pc and login.
    
  • start controller enabled game.
    
  • attempt to control game with controller.
    
  • exit game.
    
  • Leave PC overnight letting it fall asleep.
    
  • Repeat loop until controller is no longer responds.
• at this point the controller will no longer be responding.
  
• Reconnect the controller, and the result is it will now report itself as Controller 2.
  
• repeat steps for bug again.
  
• reconnect the controller. The controller will now report itself as controller 3.

The only work around for this bug is to take one of two actions...
Fix 1: Restart Steam.
Fix 2: Restart the computer ( and as a result, also restarts steam).

[austinp_valve]

When this bug happens does the controller show up as disconnecting/reconnecting or is Steam seeing multiple controllers per actual, physical device you have connected? It looks like a day or two ago there was a session where Steam saw two identical devices in No Man's Sky

[Dandeloreon]

As for some of the System state at the time the bug happens...

• I do not recall seeing any Disconnect/reconnect events.
  
• The No Mans Sky Identical devices list is showing what happens when I try reconnecting the controller while steam is active and the game is still running.
  
• I only had one controller physically connected to steam when the bug happened. I normally plug in the controller and do not disconnect the controller at all. I do have multiple identical controllers, and I only have 1 controller connected at a time most of the time.

I should mention that I have tried the libsdl2 controller test program a few months ago, and some of the output are as follows...

• reproduce the bug mentioned above.
  
• Start an instance of the LibSDL2 testgamecontroller program ( see: https://github.com/libsdl-org/SDL/blob/main/test/testgamecontroller.c )
  
• The log will clearly show the controller as player 1. There will be no other controllers.
  
• try checking input. The test program will register nothing.
  
• exit the test program
  
• reconnect the controller.
  
• run the libsdl2 test program will now show the Controller will now register as player 2.

[Madness King]

Controle ps3 e nintendo switch parou de funcionar

[Dandeloreon]

I had the bug happen just over an hour ago, and it was during the worst possible moment... While I was actively playing a game. So the following notes should be added...

• The extended driver was off when the bug happened today.
  
• The bug occurs after about 24 hours of starting steam.
  
• System Sleep does not appear to effect the issue.
  
• I had to reconnect the controller because the game was rendered completely unplayable due to phantom controller input. All input from controller freezes and the game keeps getting the same packets over and over again.
  
• Exiting the game does not fix the problem.
  
• Trying another game does not work ( all controller input is fried ).
  
• I was not actively using Big Picture mode when the controller input broke.
  
• LibSDL controller test program shows a dead controller while steam is running while effected by the bug. The program will find the controller, but receive absolutely no input.
  
• Windows only show 1 controller in device manager.

[Dandeloreon]

Just a small update after a few more days of testing that should help with some of the issue....

• Wireless Xbox One Controllers being used in Wireless Mode are generally not effected.
  
• Some Games do not properly handle Controller Disconnect/Reconnect signals, so it makes testing difficult.
  
• Wireless Controllers are generally immune to the bug due to fact the controllers automatically disconnect after being inactive for about 15 to 20 minutes.
  
• Changing from Wired mode to wireless mode after bug occurs does not help. You still haft to restart steam.