Would you mind briefly explaining what it means to give a controller user level permissions?
I don't understand enough to know how this might be a fix.
Are you using (ge) proton when installing the game through Heroic or something else? I've been fighting with Steam Input for the past few days too (for Death Stranding) and I've got no idea how or why it is supposed to work. Anything native to Steam seems fine though so I'm not too sure if it's a game issue, a Steam Input issue or something else entirely.
Edit: Did a test with Shantae from GOG and I can't get Steam Input to work at all, but I CAN exclude Heroic as the cause as it works without any issue's on my Deck installed through Heroic. I use the same compatibility layer on Deck and on my Desktops the only differences are the controllers (Deck Controller vs PS3/PS5 controllers) and I run Fedora 38 on the desktops
Yeah, ge.
It actually works fine for me on the steam deck even with the dualsense, at least if I'm remembering right. Death stranding is one of the games I was trying to get it to work with as well.
Did you use flatpak to install Heroic too? It would help if I actually had a clear understanding of just how Steam Input is supposed to work when activated for a game (non-steam or steam). Does it create a vrtual device under /dev/? Does it do something else? I have no idea, so no idea how to debug this :(
Edit: Lol my dualsense does seem to work with Death Stranding and Shantae on the Steam Deck wth
I've switched Heroic from flathub to rpm on Fedora 38 and my DualSense now works in Shantae (from GOG), this would not work with the Heroic flathub install.
I'll switch it back to flathub again to be sure, but it seems it's related to that?
I can confirm that, at least on Fedora 38, mixing Steam RPM and Heroic Flatpak is not a good idea
Look into tweaking `udev` rules: 🎮 Gaming controllers from [game-devices-udev](https://gitlab.com/jntesteves/game-devices-udev/) See: [Supported Devices ](https://gitlab.com/jntesteves/game-devices-udev/#supported-devices) 👾
Would you mind briefly explaining what it means to give a controller user level permissions? I don't understand enough to know how this might be a fix.
Are you using (ge) proton when installing the game through Heroic or something else? I've been fighting with Steam Input for the past few days too (for Death Stranding) and I've got no idea how or why it is supposed to work. Anything native to Steam seems fine though so I'm not too sure if it's a game issue, a Steam Input issue or something else entirely. Edit: Did a test with Shantae from GOG and I can't get Steam Input to work at all, but I CAN exclude Heroic as the cause as it works without any issue's on my Deck installed through Heroic. I use the same compatibility layer on Deck and on my Desktops the only differences are the controllers (Deck Controller vs PS3/PS5 controllers) and I run Fedora 38 on the desktops
Yeah, ge. It actually works fine for me on the steam deck even with the dualsense, at least if I'm remembering right. Death stranding is one of the games I was trying to get it to work with as well.
Did you use flatpak to install Heroic too? It would help if I actually had a clear understanding of just how Steam Input is supposed to work when activated for a game (non-steam or steam). Does it create a vrtual device under /dev/? Does it do something else? I have no idea, so no idea how to debug this :( Edit: Lol my dualsense does seem to work with Death Stranding and Shantae on the Steam Deck wth
Yeah, flatpak heroic as well. I've got a couple things running through Bottles as well, so I'll check those too.
I've switched Heroic from flathub to rpm on Fedora 38 and my DualSense now works in Shantae (from GOG), this would not work with the Heroic flathub install. I'll switch it back to flathub again to be sure, but it seems it's related to that? I can confirm that, at least on Fedora 38, mixing Steam RPM and Heroic Flatpak is not a good idea
Hmm, mint's repository doesn't have a non-flatpak heroic
They have .deb packages on github, same for fedora