-
-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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
Vulkan: Moving editor's windows is very laggy on linux #60106
Comments
Can you reproduce this on another desktop environment/window manager combination, such as KDE or Xfce? Also, can you reproduce this when starting the project manager with the |
Tried to launch on KDE - works great! So I guess it's GNOME's WM (Mutter) problem. Which is sucks, because I like working in GNOME.
|
I can confirm this laggy behavior in v4.0 alpha 1-6 on
On alpha 6 |
It would be good to have a dedicated bug report for the OpenGL crash, it's not related to this issue. |
I'm not experiencing the OpenGL crash with Godot 4.0-beta1, but the stuttering behavior with the Vulkan renderer is still present. Reverting to OpenGL resolves the issue for the time being. I am also a GNOME user.
I could not find any related tickets in the Mutter issue tracker, but there is one in GNOME Shell about the input delay from two weeks ago. |
Also experiencing this on Fedora 36 with Gnome using Wayland. |
Note: If I use x11 instead of Wayland everything is pretty smooth. So my guess is that this is some issue with Wayland/XWayland. |
I have this exact issue too, and it extends to 500ms-1sec delays typing text into the editor. Using beta 10. GNOME/Mutter/Wayland and Fedora 37. NVIDIA 3060 dGPU and AMD Radeon iGPU.
Running Godot with these flags set default to the AMD GPU, which is significantly underpowered but also completely solves the extreme lag. |
Fedora 36/Cinnamon here, I had similar lag, but ONLY when I had a project open. the window could be moved around smoothly but Godot's UI was laggy. This fix solved the issue for me. |
I use Linux Lite 6.2 (it uses xfce with X11, NVIDIA GeForce RTX 2060, nvidia-driver-510 (proprietary)) and the main window is very laggy.
|
I can confirm this on 4.0.rc 15a97a2 (Fedora 37, GeForce RTX 4090 with NVIDIA 525.85.05), on both Vulkan and OpenGL. I'm using KDE 5.26.5 with KWin and compositing disabled. On Vulkan, this is caused by low processor mode (which is always enabled in the project manager, but can be disabled by changing this line to The videos below are recorded at 120 FPS, so the stuttering may not be obvious when viewed on a 60 Hz monitor. I recommend viewing them in fullscreen in slow motion, or using a video viewer such as mpv to perform frame-by-frame stepping. This way, you can notice when the moved window goes out of sync with the mouse cursor (which updates at a constant rate). A suggested workaround is to trigger a redraw when the window is moved, even though this is technically not necessary (as nothing within the window is changing). This workaround may only be needed on Linux, so we don't need to suffer the increased resource usage on other platforms 🙂 If anyone is interested in reproducing the results below, you can test the project manager with Vulkan using the OpenGL with V-Sync (default project manager behavior)project_manager_opengl_vsync_on.mp4OpenGL, continuous updates with V-Syncproject_manager_opengl_vsync_on_force_draw.mp4Vulkan mobile with V-Syncproject_manager_vulkan_vsync_on.mp4Vulkan mobile, continuous updates with V-Syncproject_manager_vulkan_vsync_on_force_draw.mp4Vulkan mobile, continuous updates, no V-Syncproject_manager_vulkan_vsync_off_force_draw.mp4 |
Godot version
4.0 alpha 6
System information
Arch Linux, NVIDIA GTX750Ti, driver 510.60.02, Xorg
Issue description
Very laggy windows with Godot 4. No such problem with version 3.4.4. Could be a problem with Vulkan render. No window lags on wayland, but there is a input delay about half a second, probably because of NVIDIA poor wayland support.
Here is video:
https://youtu.be/2nGjznv3seU
Steps to reproduce
Just open Godot 4 on linux.
Minimal reproduction project
No response
The text was updated successfully, but these errors were encountered: