-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
High input latency with wgpu backend #5037
Comments
Related:
Please see if changing the value of |
Can I configure this using |
I tried changing the value here from 2 to 1 and it didn't help. |
I still suspect a latency issue with triple (or more) buffering in wgpu - maybe @Wumpf can chime in with more info |
Definitely a wgpu problem, there is no delay only if present mode is Immediate or Mailbox. |
I tested how a pure Vulkan application behaves with the FIFO present mode, which is the default for |
I'm on vacation and also not super knowledgable about the myriad of fine details here, but maybe @cwfitzgerald wants to chime in :) This sounds vaguely familiar to some issues Bevy folks reported after some severe bugs in Vulkan's synchronization code got fixed. |
I tried to show and compare what delay is present and under which API and modes, I think it will be useful. delays.compare.2.mp4 |
No, the logs say that wgpu is being used |
Describe the bug
In the demo application, there is a delay in the application's response to input: windows move with a delay, elements react to the mouse over them with a delay, and button presses also have a delay.
This issue is present in 0.28.1 and the master branch.
egui.delay.mp4
In my application, I also encountered this delay (Windows, Vulkan backend, egui-wgpu 0.28.1, and egui-winit 0.28.1). I found that the delay depends on the backend: it is lower on DX12 than on Vulkan.
I tested everything on release versions.
The web version with egui.rs works fine.
At first, it seemed to me that I was doing something wrong in my application when I encountered this issue, but since it also occurs in the demo application, it seems the problem isn't related to something else; maybe it's with egui-wgpu.
The text was updated successfully, but these errors were encountered: