-
Notifications
You must be signed in to change notification settings - Fork 50
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
wgpu Validation Error on startup #298
Comments
I've seen that error before, will try to take a look this week. |
I have encountered this bug and for me it disappeared after updating space_editor to 0.13.2. (That is, the bug was tied specifically to 0.13.1). Can you please try this PR #299 ? |
That unfortunately does not solve the issue, I get the same wgpu validation error. |
Is your windows Up to date? |
I believe it is, I had a system update a few days ago and haven't had any GPU driver update notifications popping up, but I'll check for updates tomorrow and see if anything needs to be done. |
I have everything up to date, except for my GPU drivers, which I updated before trying again, to no avail, it still fails with the same error. Here's the full log:
|
Can you try using the branch v0.6? I think my fix for this issue was merged in that branch and I don't recall what it was |
So running Do you have space_editor as a plugin and you project bevy has |
The examples in My repro crate literally has this: Cargo.tomlbevy = "0.13.2"
space_editor = { git = "https://github.com/rewin123/space_editor.git", branch = "v0.6" } # without branch v0.6 initially, added to try the branch out as mentioned above src/main.rsuse bevy::prelude::*;
use space_editor::prelude::*;
fn main() {
App::new()
.add_plugins((
DefaultPlugins,
SpaceEditorPlugin,
))
.add_systems(Startup, simple_editor_setup)
.run();
} |
edit, it seems that it only fails when I'm using the editor as a plugin in a separate project -- under the same commit, running the examples work, but running as a plugin in a separate empty project fails. I've tried matching the bevy versions (was using 0.13.2 before, and moved it to 0.13.1) to no avail. |
That is odd. We have a test for that, but it is using Linux as windows takes longer to compile. Will try to fix it |
it seems to be working in linux https://github.com/rewin123/space_editor/actions/runs/8731039708/artifacts/1424227195 |
Added a windows example to the CI, let's see if I can reproduce the error |
seems to be working fine on the new CI example https://github.com/rewin123/space_editor/actions/runs/8742952685/job/23992381723: |
That job seems to be running an example, which also runs fine on my Windows machine. It's when I use it in a separate project, added as a dependency, that it fails. This is making me think that there is probably some conflict in the dependency resolution by cargo then. |
The project is consuming bevy and space editor as external dependencies in the test. However, it is a member of the workspace for enabling rust analyzer. I tried using it as an external dependency in another project in my windows machine and was not able to reproduce it. I won't have my windows machine for the next month, so this is my limit helping with this issue. @rewin123 |
When I use the commands
.spawn((
RigidBody::KinematicPositionBased,
SceneBundle {
scene: asset_server.load("Player.gltf#Scene0"),
transform: Transform::from_xyz(0.0, 0.5, 0.0),
..default()
},
Speed(5.0),
Player,
Name::new("player"),
)) |
Sorry for late reply. Will try reptoduce bug today |
I'll try to watch it today too. Do you have the same error as the author of the issue? |
Was able to reproduce it. Indeed, at 100% screen resolution everything works, but at 125% it crashes on my Windows 10 if I run spae_ediotor as a dependency. Starting to fix it. But it works if I run space_editor in crate, weird..... |
When I ran the example, everything was fine, but when I added it to my personal demo, this error occurred. |
Hey guys, sorry I haven't been responding. I am in process of moving to another state and haven't had time to touch the project. Mid may I should be able to get back and help more |
I really apologize for the late fix. #304 fixed a bug on windows machine on my machine with 125% screen size. (Unfortunately for another two weeks I will be weakly active, as I need to conquer my PhD thesis problems if I want to defend it this year. But if there's any news on this bug, I'll get in touch and will try to add more fixes if the current one doesn't work.) |
@SolarLiner the bug should have been fixed in main |
I can confirm it works now on the main branch! |
Yay. Thanks for the cooperation! |
Describe the bug
The editor somehow causes Bevy to create an invalid viewport rect, that is outside the render target.
To Reproduce
From a blank Bevy project, add the space editor as shown on the README, and add the SpaceEditorPlugin, as well as the
simple_editor_setup
startup system.Expected behavior
Editor opens without causing a wgpu failure.
Screenshots
wgpu shows the following failure message (shown here with the DX12 backend, but is also reproducible on the Vulkan backend)
Desktop (please complete the following information):
Additional context
Removing the
simple_editor_setup
removes the validation error, but leaves the "Game View" tab empty.This bug seems to be Windows-specific, as I cannot reproduce on macOS.
As is often the case with these kinds of bugs, I have a display scale factor of 125% in my system settings, though the viewport values don't seem to nicely tie to the display value by that display scale factor, so I don't know how relevant this is.
The text was updated successfully, but these errors were encountered: