ValveSoftware / ValveSoftware/Proton

Unable to have multi controller input

Open
#6,032 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

In proton 5.x and below, I could have multiple controllers be recognized at the same times by games.
Now in later versions of proton, proton only recognizes the first available input it seems

My current setup is a wooting two keyboard and an xbox controller in arch linux and I am using the linuxconsole package
When I attempt to launch a game with proton, my wooting two keyboard running as a legacy analogue device will be the only recognized input by the launched game. In order to use a different controller I have to disconnect (disable the analogue function) in the keyboards firmware and relaunch the game with proton in order for my controller to be usable....though sometimes this also requires me to disconnect and reconnect my controller before it is recognized. disconnecting and reconnecting my controller while my keyboard is in analogue mode does nothing.

Udev recognizes both devices can be used at the same time and so does the old JS method, steam sees both my wooting two and my xbox controller as input methods as well.

Im not sure what else to provide for troubleshooting

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named. Start by reproducing the issue with the Wooting Two in legacy analogue mode and an Xbox controller on Arch Linux, comparing Proton 5.x with a later version. Done means both input devices are recognized simultaneously without disconnecting or relaunching the game.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.