Steam Deck - No inputs are detected if controller disconnects
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
When you have a Bluetooth device connected to the steam deck. Disconnecting and reconnecting it causes RetroArch to not show any devices connected in the Port Controls settings. This causes an issue of the reconnecting controller being set to port 2 and having no way of changing, which port it is on. The System Information screen shows that the input devices are connected to ports. The problem is that you can not change, which ports they are connected to since the Device Index does not appear to show them.
Expected behavior
I expected the correct number of inputs be available in the Port Controls settings.
Actual behavior
I get no inputs or sometimes only 1 input in the Port Controls settings, Device Index.
Steps to reproduce the bug
- Connect a Bluetooth controller.
- Play a rom.
- Disconnect then reconnect the Bluetooth controller.
- If you check RetroArch input settings, in every Port Controls settings the Device Index will contain no controllers.
Version/Commit
You can find this information under Information/System Information
- RetroArch: Git https://github.com/libretro/RetroArch/commit/389ef31, Build Oct 4 2022
Environment information
- OS: SteamOS 3.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Bluetooth controller disconnect and reconnect sequence on SteamOS 3.2, then inspect the input handling behind Port Controls and Device Index. Done means the reconnected controller appears in the available devices and can be assigned to the correct port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100