Skip to content
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

Prefer wayland over X11 #16

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

jsparber
Copy link

@jsparber jsparber commented Apr 4, 2024

Always try to use wayland and fallback to X11 only when wayland isn't available.

This fixes the "Unvanquished is potentially unsafe" warning on flathub.

Always try to use wayland and fallback to X11 only when wayland isn't available.

This fixes the "Unvanquished is potentially unsafe" warning on flathub.
@flathubbot
Copy link

Started test build 112245

@flathubbot
Copy link

Build 112245 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/95059/net.unvanquished.Unvanquished.flatpakref

@necessarily-equal
Copy link
Collaborator

Hello! Thanks you for your interest.

Last I checked, we still had some problems with the wayland display protocol. Although they do not seem to be critical, I think we should at least fix some of them before we switch. Those issues are tracked in DaemonEngine/Daemon#482 (I've just updated it a bit).

The most annoying issues would be Unvanquished/Unvanquished#1887, and maybe the (alleged) framerate drop DaemonEngine/Daemon#484.

Most of these issues seem to need some triaging to check if they are still causing trouble, would you be willing to help on that? This means checking if the issues still exist, and if you experience those yourself 😃

@jsparber
Copy link
Author

jsparber commented Apr 5, 2024

Not sure, how much time i have to look at this. I was mostly annoyed about the warning on flathub :)

@necessarily-equal
Copy link
Collaborator

necessarily-equal commented Apr 5, 2024 via email

@necessarily-equal
Copy link
Collaborator

I tested on Wayland a bit while working on #17 and I still noticed the bug where in game, the cursor disappears on Wayland until it hoovers on top of a window. See Unvanquished/Unvanquished#1887 (comment) for more details on that bug.

For now I'd say X11 still works a little bit better, and is definitely better tested, so I didn't change the default just yet.

By the way for me this PR didn't work out of the box. To get the Wayland backend working at all when X11 was disabled, I had to pass SDL_VIDEODRIVER=wayland,x11 as an environment variable as well. This led me to notice another bug, fixed in 53c51d4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants