-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Broken rendering wireframes on windows / DX12 #10019
Comments
I think just reverting for now is likely the safest choice, but if y'all can find another fix I'm happy to take a look. |
I don't think this is a new bug, the PR didn't touch any rendering code. I just tested it with bevy before the PR and wireframes were already broken with DX12 |
I can't test locally DX12, but it's running as part of https://vleue.com/bevy-example-tests/index.html |
So, I'm not entirely sure what the issue is yet, but I know why this tool didn't show you the error. It only shows up on the plane mesh but before that PR the plane was disabled. I needed to enable the global wireframe to show the issue. |
I'm still digging, but 0.11.3 works correctly but 20ed3e0 doesn't |
To be clear, this only happens with the DX12 backend, Vulkan backend is fine. Technically it's also broken on the webgpu backend, but line drawing isn't supported on that backend so the fact that it renders anything is a wgpu bug that will be fixed. |
# Objective - Fixes #10019 ## Solution - Uses a workaround for DX12
I was going to say - it looks like it's loading the wrong transforms from instance data, and I remembered that there was an instance index workaround for DX12 misbehaviour. |
# Objective - Fixes bevyengine#10019 ## Solution - Uses a workaround for DX12
# Objective - Fixes bevyengine#10019 ## Solution - Uses a workaround for DX12
# Objective - Fixes bevyengine#10019 ## Solution - Uses a workaround for DX12
Originally posted by @mockersf in #7328 (comment)
The text was updated successfully, but these errors were encountered: