Skip to content
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

Open
dyllan500 opened this issue Nov 9, 2022 · 3 comments

Comments

@dyllan500
Copy link

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

  1. Connect Controllers.
  2. Launch RetroArch.
  3. Launch a Game.
  4. Disconnect then Reconnect controller.
  5. Use the reconnected to controller to check the input settings and see that it is no longer shown, but the input works in the menus.

Version/Commit

Environment information

  • OS: SteamOs 3.2
@martyfuhry
Copy link

Looks like the same thing as #14524.

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.

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.

@Sieb87
Copy link

Sieb87 commented Sep 20, 2023

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:

  • Hit the Steam button on the Steam Deck, it will show overlay with the controller settings
  • Turn on the controller again and wait for it to reconnect.
  • Resume RetroArch by selecting 'Resume Game' using the controller.
  • I'm now able to use the controller again.

I only use one controller so not sure if this works for everyone.

@martyfuhry
Copy link

Thanks for the workaround steps! Unfortunately, it didn't quite work for me... Below, I put in my exact reproduction steps:

  • Launch a RetroArch game from Game Mode on the Steam Deck (I had EmuDeck add the games for me, they just launch RetroArch)
  • Disconnect the controller (sleep the Steam Deck and immediately turn it back on)
  • Hit the Steam button on the Steam Deck
  • Turn on the controller again and wait for it to reconnect
  • There's no "Resume Game" option for me on RetroArch
  • The game continues running but does not respond to any input
  • Controller is recognized by Steam Input
  • Steam Deck Controls don't work in game

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants