-
-
Notifications
You must be signed in to change notification settings - Fork 21.2k
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
[TRACKER] Wayland issues #88346
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Edit: , I am not confident it isn't a KDE related issue, but am not in a position to test it on other DE's currently. This is an example: https://youtu.be/Xr5cmBRonls Has anyone ran into a really strange issue where trying to resize a windowed instance of Godot under Wayland/KDE causes it to move way up off the top left edge of the screen at a massive scale? It does not replicate under X11, but it is such a strange thing I don't really have enough to file a useful report. I am using a laptop display at 2256x1504 and a desktop monitor at 2569x1440. I have confirmed it does not matter if the second display is connected or not, the issue still occurs with only the laptop display connected. This was all found using the git build of Godot as-of 4/8/24, it is not present in stable. Update: I have narrowed this down to being introduced between cd4e4c0 and b926e51. Narrowing down still. |
This comment was marked as resolved.
This comment was marked as resolved.
Hi folks, sorry for the delay, I couldn't work on this stuff in the last few weeks. I just got back! :D @Roogephy thanks for the report! I'll explain the situation a bit more thoroughly there once I get back to speed. I'll put the issue in the tracker and mark the relevant messages as "resolved" to not clutter the thread too much. Hi @BiosElement, this issue feels quite complicated and I'm not sure how the bisected commits relate to this at all. That said, I recommend to file a dedicated issue ticket so that we can investigate further without cluttering up this thread. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, but does anyone else "feel" a difference between regular and "Prefer Wayland" setting? I don't know how to see the framerate of the editor, but I have a 120hz display and it feels like 20-30 when I enable Wayland (but other apps are fine and mouse gestures are super smooth too). This is using "single window mode" as well, btw. |
@eobet sorry for the delay. That's quite weird. You could try running the editor directly by opening a You should then see the framerate being printed into the standard output every few seconds. If there's a substantial difference in framerate between the wayland and the x11 backend, please file a new ticket.
Note that, due to various reasons, the Wayland backend is forced to the single window mode for the time being. I'm researching the steps needed for a proper multi-window implementation. If you see multiple native windows, then you're running the X11 backend through XWayland. |
Tested versions
System information
Linux/BSD - Wayland backend
Issue description
A new, experimental and opt-in Wayland backend got merged in 4.3.dev3.
While it got tested plenty, there are still quite a bunch of missing features and lots of things to improve, which are tracked in this issue.
Tasks
TIME
is unreliable (slow shaders) due to frame pacing method #87963DRI_PRIME
warnings raised by DetectPrimeEGL #88364opengl3_es
rendering driver #91371app_id
throughout its execution #96074Steps to reproduce
From the CLI: start the engine with the
--display-driver wayland
flag.Alternatively, for the editor: set the
run/platforms/linuxbsd/prefer_wayland
editor setting totrue
or, for running projects, set thedisplay/display_server/driver.linuxbsd
project setting towayland
.Minimal reproduction project (MRP)
N/A
The text was updated successfully, but these errors were encountered: