testing samples: rendering to device is not working #366
Comments
karroffel
added
C-Bug
|
I'm getting this same issue. Also on a laptop, both with and without my external monitor. |
|
My issue is happening at a different line of the same file, so it may have a different cause, here's the path trace: |
|
I do have both an intel & an amd GPU on this laptop, in case that's relevant. |
|
Same on my machine |
|
still the same after cargo update sidenote: the wgpu-rs samples are working |
|
Also would be great to know how to force wgpu to use vulkan instead of directx |
|
thanks to some help in discord @MGlolenstine adviced me to revert c42dad5 |
|
@fopsdev you shouldn't have to revert that, looking up both your integrated and dedicated graphics, your radeon has better support for DX12 than your uhd620. Have you tried updating your drivers, and have you tried other dx12 software on that computer? (also since its a laptop i assume prebuilt, can you link your computer?) also, doesn't look like bevy exposes the feature flags for wgpu, but you should be able to add them to bevy_wgpu, then do the main bevy crate to try vulkan or whatever. |
|
@Dispersia - In theory, the same is true for my laptop. However, it still crashes when I try to use my radeon. The problem seems to be in wgpu - even the wgpu-rs examples fail if I attempt to have it use the Radeon graphics card. |
|
have you tried updating drivers as well? also would still like a link to the laptop, to see default driver versions |
|
@Dispersia, MGlolenstine here. I've advised on reverting the commit because of problems with driver installation. I'm assuming that either Windows10, MOBO's chipset or wgpu code are causing problems. Problems could be solved by installing chipset drivers or somehow tricking GPU drivers to install correctly. It could also be something that we haven't thought of yet. wgpu works fine on my RX 580(desktop gpu), so it has to do something with a laptop. @lee-orr does your computer use the same Intel + AMD combo? |
|
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. |
|
Hi there let adapter = instance
.request_adapter(&wgpu::RequestAdapterOptions {
power_preference: wgpu::PowerPreference::HighPerformance,
compatible_surface: None,
})
.await
.unwrap();with the one from wgpu-rs let adapter = instance
.request_adapter(&wgpu::RequestAdapterOptions {
power_preference: wgpu::PowerPreference::HighPerformance,
compatible_surface: Some(&surface),
})
.await
.unwrap();but the difference is that wgpu-rs uses a initialised UpdateOk false alarm regarding |
|
@Dispersia |
|
It is still most likely a driver issue. GPUs have features they add in their drivers, and bevy is probably using something your driver is falsely reporting as working, while the base examples are not. |
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:
I'm on Win10 with a decent relatively new notebook.
It happens as well when i disconnect my external monitor
Its maybe related to: #340
DxDiag.txt
The text was updated successfully, but these errors were encountered: