this post was submitted on 14 Aug 2024
14 points (100.0% liked)

Linux Gaming

14954 readers
43 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 1 year ago
MODERATORS
 

EndeavourOS (Arch Linux) user here.

Is this just me? Everything works perfectly, but if the controller turns off and on again while a game is running, it's no longer recognized, and this forces me to restart the game.

I don't know how useful it is but I tried to join the input group, nothing changed.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 month ago (1 children)
[–] [email protected] 1 points 1 month ago* (last edited 1 month ago) (1 children)

Yes, bluetooth. The controller is seen again by the OS and then by Steam but not by games already started.

[–] [email protected] 3 points 1 month ago

I'm betting this has to do with your OS settings for two things:

  1. Bluetooth device sleep settings
  2. ID mapping for BT devices

If X minutes lapses without activity, your OS may put some device and device controllers to sleep, like USB and BT devices. Install 'powertop' and look to the tunables tab to see which has which.

I would also have a look at the deviceid of the Bluetooth controller while it's working, and then check again afterwards. I think you can use 'bluemon' as an easy tool for that, but whatever works. If the ID changes, then it's possible steaminput isn't paying attention to it.

Depending on your OS, you may have to install some compatibility tools for Steam as well. On Debian-based, it's called 'steam-devices', but there are others that work as well. See the Flatpak section here: https://wiki.archlinux.org/title/Steam about 'steam-devices'.