Skip to content
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

Window resizing weirdness with dx12 #1061

Closed
Diggsey opened this issue Nov 28, 2020 · 3 comments
Closed

Window resizing weirdness with dx12 #1061

Diggsey opened this issue Nov 28, 2020 · 3 comments
Labels
external: driver-bug A driver is causing the bug, though we may still want to work around it type: bug Something isn't working

Comments

@Diggsey
Copy link
Contributor

Diggsey commented Nov 28, 2020

On windows 10, I see this after I resize the window:
image

The text is my terminal somehow showing through the window in front of it...

When I run the "hello" example, it prints:

AdapterInfo { name: "Intel(R) UHD Graphics 620", vendor: 32902, device: 22807, device_type: IntegratedGpu, backend: Vulkan }

If I move the window by dragging the titlebar, the issue fixes itself until I next resize.

I tested all the examples, and strangely the issue only happens on the cube example. This seems to be because the other examples default to using vulkan as the backend, but the cube example uses dx12 instead?

Furthermore, this issue does not occur if I manually change the backend to "dx11" or "vulkan".

@Diggsey
Copy link
Contributor Author

Diggsey commented Nov 29, 2020

Now we know why it uses dx12 instead of vulkan, I tested the other examples on dx12, and they also exhibit the same problem.

edit: "hello-triangle" does not have this issue.
edit2: that's just because it ignores the env var to set dx12

@Diggsey Diggsey changed the title Cube example window resizing weirdness with dx12 Window resizing weirdness with dx12 Nov 29, 2020
@cwfitzgerald cwfitzgerald transferred this issue from gfx-rs/wgpu-rs Dec 1, 2020
@cwfitzgerald cwfitzgerald added external: driver-bug A driver is causing the bug, though we may still want to work around it type: bug Something isn't working labels Dec 1, 2020
@cwfitzgerald
Copy link
Member

@Diggsey if I'm correct this was fixed by updating your intel graphics drivers? I think we can likely close this as there's not much we can do if intel was misbehaving behind window's back. Feel free to re-open if that's not satisfactory.

@Diggsey
Copy link
Contributor Author

Diggsey commented Dec 1, 2020

Yep - this is now listed here: https://github.com/gfx-rs/wgpu/wiki/Known-Driver-Issues#intel--directx-12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external: driver-bug A driver is causing the bug, though we may still want to work around it type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants