bevy: testing samples: rendering to device is not working
Hi there
I would like to run the examples and fiddle around with them. But every example which is supposed to render something is failing.
Expected behaviour:
cargo run —example breakout -> run breakout
Current behaviour:
window is unresponsive. and rust (and myself a bit 😉) panicks out backtrace if its of any use:
C:\dev\test\bevy\bevy>cargo run --example breakout
Finished dev [unoptimized + debuginfo] target(s) in 0.30s
Running `target\debug\examples\breakout.exe`
thread '<unnamed>' panicked at 'assertion failed: `(left == right)`
left: `0`,
right: `-2005270523`', C:\Users\fopsd\.cargo\registry\src\github.com-1ecc6299db9ec823\gfx-backend-dx12-0.6.2\src\device.rs:2242:9
stack backtrace:
0: std::panicking::begin_panic_handler
at /rustc/f44c6e4e288e4f49c5c257b2e2cb2ad5918f26a3\/library\std\src\panicking.rs:475
1: std::panicking::begin_panic_fmt
at /rustc/f44c6e4e288e4f49c5c257b2e2cb2ad5918f26a3\/library\std\src\panicking.rs:429
2: gfx_backend_dx12::device::{{impl}}::bind_buffer_memory
at C:\Users\fopsd\.cargo\registry\src\github.com-1ecc6299db9ec823\gfx-backend-dx12-0.6.2\src\device.rs:2242
3: wgpu_core::device::Device<gfx_backend_dx12::Backend>::create_buffer<gfx_backend_dx12::Backend>
at C:\Users\fopsd\.cargo\registry\src\github.com-1ecc6299db9ec823\wgpu-core-0.6.0\src\device\mod.rs:438
4: wgpu_core::hub::Global<wgpu_core::hub::IdentityManagerFactory>::device_create_buffer<wgpu_core::hub::IdentityManagerFactory,gfx_backend_dx12::Backend>
at C:\Users\fopsd\.cargo\registry\src\github.com-1ecc6299db9ec823\wgpu-core-0.6.0\src\device\mod.rs:969
5: wgpu::backend::direct::{{impl}}::device_create_buffer
...
...
I’m on Win10 with a decent relatively new notebook. It happens as well when i disconnect my external monitor
Its maybe related to: https://github.com/bevyengine/bevy/issues/340
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (9 by maintainers)
Different one - mine is a Radeon RX Vega M GL card (embedded on the die w/ the intel CPU). These ones haven’t had a driver update in a while, even though they are only a couple years old. But I was experiencing the same issue, and the same solution worked for me.