Reduce input latency by switching to double-buffered rendering #4575
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
I also switched the defaults in
eguo-wgpu
: emilk/egui#3714Checklist
main
build: app.rerun.ionightly
build: app.rerun.io