-
Notifications
You must be signed in to change notification settings - Fork 938
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
Resizing on macOS is cursed again #1168
Comments
Some idle thoughts, I'm fairly sure that this happens because of combination of
Avenues to look at,
I wonder if that happens also with other winit using projects? |
It does. Glutin has the same issue, and they also use winit: rust-windowing/glutin#1340 I'll open an issue in winit's repository to see if they can implement number 2 (handling resize events synchronously). |
This issue is not solved yet. Redrawing immediately inside of the Resized event still results in this stretching, even on the latest winit... so this may be a wgpu issue, assuming winit is doing its job correctly now. |
Actually it seems now to be the reverse of what it was before. In my newest commit LoganDark/wgpu-stretch@517a37b I updated to the latest (git) version of Now it seems that the frame is being presented before the window's new size is applied, which I initially thought could be solved by using the |
I prototyped a potential fix for this in gfx-rs/gfx#3627, but it didn't work at all 😓 |
You could check out gfx-rs/gfx#3627, enable the override to use it, and see if it helps. |
Looks like this is still an issue with https://github.com/lapce/lapce/ on Windows |
|
Yeah this seems like a latency based race - we currently have no way of canceling presentation yet, which is potentially what you'd need to do with pending presents which hit the surface after the resize happened. |
So
|
Description
When resizing the window, the previous frame is stretched before any new frames are displayed. Or... maybe a new frame is drawn using an outdated uniform buffer and I can't update it in time. Who knows...
Repro steps
https://github.com/LoganDark/wgpu-stretch
Expected vs observed behavior
The square in the top left should not stretch
Extra materials
The previous incarnation of this bug can be found at #249
Platform
macOS 10.14.6 Mojave
Tech stack is as described in the wgpu-stretch repository
The text was updated successfully, but these errors were encountered: