Replies: 1 comment
-
So Ive tried adding adding dbus socket to the container, adding udev rules on the host, installing bluez in the container, adding any volume i can think of that might be linked to controller input (that isnt already added) and while the container can see the controller just fine steam cant until it is closed and relaunched. Trying to figure out by what means steam handles controller detection/hotplugging EDIT: Looks like it might be related to SDL, it seems anything using SDL for gamepad fails to detect it within the container. Steam and Ryujinx both cant but RPCS3 which can use EvDev has no problem |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I use Distrobox on Fedora SilverBlue to run steam as i need to have an easy way to read game memory when using timers that hook into the game and flatpak cant do this.
This so far works perfectly except for one single issue, Steam cannot detect when a controller has been connected via bluetooth. Ive been searching around using my google foo but i havent encountered any real discussion on this.
I created the container as follows
distrobox create --name "cont-name" --volume "games drive volume"
Is there perhaps something else i need to pass to the container to allow steam to see the controller without having to have it connected before steam starts?
Beta Was this translation helpful? Give feedback.
All reactions