protonscr

Nintendo Switch Pro Controller losing input during rumbling

protonopen
ValveSoftware/Proton#2898 · opened 2019-07-20 by Vash63 · updated 2020-05-24 · 4 comments · github
VVash63 2019-07-20 github

Your system information

  • Steam client version (build number or date): Jul 18 2019 at 00:11:36
  • Distribution (e.g. Ubuntu): Arch
  • Opted into Steam client beta?: Yes
  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

When any action causes the Switch Pro Controller to rumble, all input is frozen in its last state. This is when using the Steam Input configuration to emulate an X360 controller, for both native and wine games.

Examples:

  1. In DMC5 in Proton, if I tap left or right on the menu to enable rumble, it continually toggles it until I unplug the controller.
  2. Searching for scan points from the ship in Mass Effect Andromeda via wine (using Switch controller mapped in Steam Big Picture -> Base Configuration -> Desktop Configuration), when I hold ZR for scanning it rumbles to let you know how close you are - at this point all input is lost until I hit something on the keyboard to interrupt the rumble (such as esc to the menu or whatever button does the same thing as ZR / right trigger on the gamepad), at which point input on the controller works again.

Update: Not sure about native Linux actually on further testing, this might only impact Wine/Proton. I cannot duplicate the error on html5gamepad.com even when it's detecting my controller as an X360 pad via Steam Input.

VVash63 2019-07-20 github

steam-253230.log.gz

I was able to duplicate this in Hat in Time by head diving into a wall and then trying to pause the game or turn the camera during the rumble.

AAwesamLinux 2019-07-21 github

I have been having issues with Nintendo Switch Pro Controllers over Bluetooth with Kernels later than 5.0.13.

The issues I have experienced:

  1. The controller needs to be re-paired after every reboot using Kernels 5.0.14 or newer. Often also the pairing fails.
  2. Connection with controller drops out in games using rumble.
  3. Steam thinks controller has not been used and turns it off (after the set amount of time, so you have to set the timer high but then you drain the battery)

I think the controller dropping out in games using rumble has possibly been fixed in recent Steam versions, or at least the issue has been reduced. It used to happen all the time before, but now I have had some pretty lenghty sessions without seeing that problem.

system_info.txt

The motherboard is a Asrock Taichi X399 that has Intel® 802.11ac WiFi

AAwesamLinux 2019-07-27 github
  • GPU: RX VEGA 56
  • Driver/LLVM version: 19.1.0+aco+git1564050652-58e0420cb35-1bionic1 (Valve-Experimental PPA)
  • Kernel version: 5.2.3-050203-lowlatency
  • Distro version: Linux Mint 19.1 Tessa (64 bit) (Cinnamon Desktop)
  • Proton version: 4.2-9
  • System information: system_info.txt

I did some re-testing with recent Kernel/Mesa/Steam Client. Adressing my previous issues mentioned:

SUCCESS! The controller no longer needs to be re-paired with each reboot with more recet Kernels, no problems when I tested with Kernel 5.2.3 and 5.1.19

FAIL! Connection with controller drops out in games using rumble. Easily replicated with Redout Enhanced Edition. When rumble is enabled the controller disconnects usually after 1-3 races. Disabling rumble in the settings of the game, I could play many races without that happening.

Including two logs of the controller dropping out when playing Redout with rumble enabled:
steam-517710_control_drop1.log
steam-517710_control_drop2.log

Jjohntyree 2020-05-24 github

This doesn't seem to have anything to do with Steam. I am playing stadia games with a Switch Pro Controller without Steam running at all (although it is installed) and having the same issue.

Nothing extracted yet.