-
Notifications
You must be signed in to change notification settings - Fork 392
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 latency hover in macOS Chromium with OpenGL backend #2672
Comments
I fail to reproduce: I only get one frame of latency, not at all as bad as the video (btw: you can embed mp4 videos by drag-dropping them into GitHub). Have you tested it in the native viewer? What web browser are you using? Does the size of the browser window affect the latency? |
This makes a huge difference in perceived latency on my 60 Hz monitor on macOS on a native build, e.g. when hovering buttons, or just the distance between the cursor and the hover-window when hovering an image. It does produce some tearing, noticable e.g. when quickly panning a 2D image. To me the trade-off is absolutely worth it: tearing is a mild visual glitch that shows up occationally, input latency is a constant irritation, making an application feel sluggish. It makes no difference on web though, so this does NOT solve #2672
This seems to only be affecting Chromium on macOS with an OpenGL backend. Workaround:
This should only be a problem with the WebGL version of our web-viewer, so once we use WebGPU as our primary choice (hopefully soon in 0.12), then this problem should go away. |
Describe the bug
The hover state in the navigation is delayed and makes the app feel sluggish.
To Reproduce
Quickly hover the menu items.
Expected behavior
The hover state should toggle instantly on mouseenter/mouseout.
Screenshots
https://github.com/rerun-io/rerun/assets/875708/2a34aacd-187d-4fe1-8311-ed13b9ecd249
Desktop (please complete the following information):
OS: Latest MacOS
Rerun version
app.rerun.io/commit/5311903
Additional context
I'm using a high resolution, 5K display.
The text was updated successfully, but these errors were encountered: