-
Notifications
You must be signed in to change notification settings - Fork 130
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
Does not work on Wayland #737
Comments
Not sure if this applies to this version, but in ryochan's fork https://github.com/Ryochan7/sc-controller to get it working in wayland you need the additional packages gtk-shell-layer and libappindicator-gtk3. Hope this helps. |
But Ive also found that the gui does not launch while in Wayland, despite the program working in the background along with the task tray icon and menu mode. So right now if using sc-controller you would need to go into the x11 desktop session to configure the controller, then switch back to wayland. The menu mode also does not appear on top games, but behind it. Hope this gets fixed. |
Btw the current fork is https://github.com/C0rn3j/sc-controller, Ryochan7 archived theirs in the beginning of this year. Wayland OSD seems to work for us, but virtual keyboard is still segfaults. But it requires Layer Shell extension which GNOME's Mutter refuses to support. |
Hi!
I've been using it with my Steam Controller on Gnome X11, when i had Nvidia. Worked fine.
Now i switched to an AMD card and Wayland, and no input from the controller is recognized, the menu doesn't show up when i press the guide button, nor does it do any inputs, Desktop or Xbox configurations, mouse doesn't move, no buttons do anything, nothing.
Is the program just not working with Wayland in general or is this a separate issue?
In any case, i thought i'd report this as i'd like to keep using it. It's my go-to for Heroic Launcher games where Steam doesn't work well.
If you need me to post some logs or something like that, please tell me what to do.
Using Arch Linux, Gnome Wayland, sc-controller version 0.4.8.13
The text was updated successfully, but these errors were encountered: