-
Notifications
You must be signed in to change notification settings - Fork 197
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
[Feature request] Support for Wayland clients #543
Comments
This sort of thing is why you couldn't run OBS Studio in game mode by default. It is detected as a Wayland session, but the fact that Gamescope doesn't actually support Wayland clients causes it to just immediately crash. Either gamescope should support Wayland clients, or it should not advertise itself as a Wayland session. EDIT: As to the OP's concerns, it is worth noting that you're not actually running Xorg when you set SDL_VIDEODRIVER=x11. All applications go through XWayland. But then I have to wonder... why do any of the applications with backends that support Wayland work at all right now, if Gamescope is detected as Wayland without actually supporting Wayland clients? |
We do not advertise support for xdg shell. |
I'm presuming XDG Shell is what most other applications check to determine if they are running in a Wayland compositor. Then, in that case, do you think that Qt 6--the toolkit that OBS Studio is using--is doing something wrong? |
Yes, Qt6 should check if xdg-shell is supported before trying to use it, and fallback to X if not. |
We don't have this problem with other Qt apps though, so, strange... maybe its something OBS is doing instead? Have we determined its Qt and not say, wayland video capture plugin, etc? |
Potentially? It seems like OBS team is also unsure whether it's them or Qt. I'm pretty sure "Wayland video capture" is just Pipewire--and as far as I know, Pipewire-based video capture should also work on X11 anyways--but it doesn't, not on KDE Neon nor on SteamOS. |
Dragging in a loose end from #668: Whenever Wayland clients are fully supported, that should include support for text-input-v3 so that the on-screen keyboard can continue to work, as it now does with SDL's x11 driver: (FWIW, SDL supports systems without xdg-shell, it just happens to be that xdg-shell gives us a lot of useful stuff, but gamescope won't care about most of this. I encourage anyone focused on this task to look at SDL's Wayland folder to evaluate the tradeoffs: https://github.com/libsdl-org/SDL/tree/main/src/video/wayland ) |
I also recently found a use case for supporting Wayland clients. I've been tinkering with Wine patched with Wayland support, and GNOME freaks out when some games are running with it, showing the window in a weird way. |
Support for xdg-shell was added: #759 |
Qt6 applications don't appear to work correctly with |
As the title says, Gamescope needs to add support for Wayland clients
For example If you try to run a SDL2 game with
SDL_VIDEODRIVER=wayland
under gamescope, then gamescope won't touch it at allRunning it with
SDL_VIDEODRIVER=x11
makes gamescope actually work with it, but I don't like running an outdated display server if a game can natively run on WaylandI wonder how hard this would be to achieve because you use wlroots (I've tried running nested
sway
with the output scale set to below 1 for one of gamescope's nice features (aka downsampling) and it kinda works but it's a bit of a mess with having to resize a microscopic terminal and the mouse spins in circles in the few games I tried)Edit: Apparently this topic was mentioned in #164, but it wasn't a feature request
The text was updated successfully, but these errors were encountered: