retroarch-snap
retroarch-snap copied to clipboard
Controller Issues in 18.04
Hello!
I have had trouble using a controller with my snap of retroarch. I am using a wired Xbox 360 controller and the udev input driver. lsusb shows that the device is present and the controller lights up and has the led for player one lit. No matter what I do, input 1 seems to always have a null input device index.
I have run the two snap commands (listed below for completeness) to add usb support and have also run snap refresh to make sure nothing needed up updating.
sudo snap connect retroarch:raw-usb
sudo snap connect retroarch:joystick
Can you please help me see if I am missing something? TIA!
I can verify this. Also, both the version from the repo and the Flatpak from Flathub detect the controller.
In my experience, autoconfig wouldn't work. I had to use the regular mapping in settings > input > p1 input binds, but after that I was able to play.
For you now we will need to update the core to edge branch. Can you try
sudo snap refresh —edge core
This seems to be a permissions issue, in the ubuntu software gnome-software package, if you installed retroarch via that, go and modify the permissions next to the "remove" button.
Hi! We spoke to the Snap Security Team. It's perfectly reasonable for a game (or emulator) to have the joystick interface auto-connected on install. Requests for auto-connected interfaces are done in the open, on the snapcraft forum.
Please could someone from the upstream project make a request on the forum and it will get reviewed / approved / actioned in the store, so future installs and updates will not have to manually connect the joystick interface. Thanks!
We have been granted automatic joystick connection right so it should work now.
@oaguy1 @Mister-Dolus Using latest snap, can you use your controller ?
Faced similar issue. just turned out that I had to do this. go to the settings tab hit drivers and change the input and joy pad driver to sdl2 now just configure the controller Now it works flawlessly. I was using redgear pro controller and it has fixed this.
@oaguy1 Is this still an issue otherwise please close this issue.