-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Steam] Launching RetroArch using Steam on Linux Does not Allow Controllers to Reconnect #14608
Comments
Looks like the same thing as #14524.
This is a very interesting find, however! Maybe that will narrow down the search for the bug, since I believe Steam Input handles all of the controllers, right? If that's correct, and if RetroArch handles reconnecting controllers just fine when not launched through Steam, then the issue probably lies in how RetroArch handles Steam Input. |
I'm having the same problem as described by dyllan500. I was able to reconnect a controller by following the exact steps below. I hope this can help to narrow down the exact issue a bit more. When in RetroArch and controller lost connection:
I only use one controller so not sure if this works for everyone. |
Thanks for the workaround steps! Unfortunately, it didn't quite work for me... Below, I put in my exact reproduction steps:
The only solution is to quit the game from the Steam button menu for me. I wonder if you are using the EmuDeck stock configuration or if there's something different between our setups. |
Description
When launching RetroArch using Steam, either through the steam store, or adding the flatpak version as a non steam game and launching it that way. While playing a game if a controller gets disconnected, then reconnected. It does not show up in the input device settings. Even though the controller can control the RetroArch menu. The input is missing from the device index in the input settings.
However if you launch the flatpak verison without using steam this not an issue. The controller shows back up in the input settings and everything works great.
I have tested this mainly on the Steam Deck but my Desktop computer running Linux as the same issue. I am not sure if it is Steam that is causing the issue. It would be nice if this issue was fixed, because launching RetroArch using steam in game mode is the best way to use RetroArch on the Steam Deck.
Expected behavior
The expected behavior is when a controller disconnects and gets reconnected. It should show back up in the Input settings as a usable device.
Actual behavior
What actually happens is when a controller gets disconnected and reconnected
Steps to reproduce the bug
Version/Commit
Environment information
The text was updated successfully, but these errors were encountered: