-
Notifications
You must be signed in to change notification settings - Fork 1k
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
DEVICE_REMOVAL_PROCESS_AT_FAULT because DXGI_ERROR_DEVICE_HUNG on W10 with HD 4600 #4007
Comments
See #3604 (comment). I don't know why they are still advertised as supporting dx12. |
Looking at the release notes for the driver version 15.40.44.5107 those iGPUs are still listed as supporting dx12 contrary to my reading of https://www.intel.com/content/www/us/en/support/articles/000057520/graphics.html (or do they mean versions higher than 15.40.44.5107 but not including?). The next version 15.40.45.5126 correctly advertises them as supporting 11.1. Can you let us know which driver version you have? |
Based on task manager it's Edit: Same thing on GPU-Z |
That seems to map to 15.40.48.5171 which is the latest version (not sure why there are 2 kinds of versions; if you click on the readme on the page I linked it's listed as 20.19.15.5171 instead). Since you are on the latest version, are you still seeing this issue or is the iGPU now no longer selected by wgpu? |
In some examples yes, other no.
|
Are you sure that the examples are running on DX12 on the iGPU? (try to run them with The following is noted in the driver release notes. Can you let us know what those versions are ("Installed DirectX* version" & "Supported DirectX* Version")?
I suspect DX12 support might still be there but the hardware might be on FL11.1 and we are missing some checks. |
I re-ran the examples, all of them run on vulkan on the dedicated GPU
Here's whats written:
|
I tried rerunning them by force using environmental variables. bevy's breakout didin't run with the iGPU but otherwise ran fine with some warning, here's a log: wgpu's skybox ran with the iGPU but crashed, here's the log: PS: The logs are too big so I uploaded zip files with the logs inside them as txt files |
The env variables are only guaranteed to work with wgpu's examples.
This one seems to fail with the same error.
|
So, I'm starting to think that FL12 functionality got deprecated for those iGPUs but they should still work since we should be supporting FL11.1. The error seems to always happen at buffer creation. @cwfitzgerald do you think we might be trying to use some functionality that's not available on FL11.1? |
Also found #1319 & #849 which seem related. kvark's comment #849 (comment) suggests getting more logs via DebugView or through Visual Studio (see https://github.com/gfx-rs/gfx/wiki/Debugging-D3D#log). |
I reran the skybox example with both VS and DebugView, here are the logs: wgpu_skybox_log_DebugView.zip The zip files contain 2 files. One of them is the rust log, the other is the VS/DebugView ouput Edit: I just realized that some errors in the VS output are not related to the program, idk how they got in |
It doesn't look like there is anything new in those logs. Not sure what to do next... We might end up fixing this in our quest for #2719. I will add it in the "There are some driver issues that we may not be able to fix, but we should keep in mind:" section for now. |
Hi, I don't know where to set the version of |
Haswell iGPUs will no longer show up in the adapters list instead of erroring with "device is lost" whenever any operation is ran on them. |
Okay, I see, but what is the larger picture? Does that mean that wgpu and by proxy Bevy will not support these iGPUs? |
They will fall back to our OpenGL support. |
Ah, okay, thanks! |
Description
Hi, I'm getting this error when running Bevy's breakout demo. A window shows up for a second or two, then disappears. I assume the error is something to do with wgpu, since most of the output seems to originate from it.
Repro steps
I ran the
cargo run
command on thelatest
branch of Bevy. I assume either my hardware isn't supported, or perhaps it's some software not being present on my computer.Expected vs observed behavior
I'm mainly just unsure what is the issue. Could you clarify whether it's that my GPU is unsupported, or it's just a bug? The error isn't very clear about what the case is 😅
Platform
Windows 10, wgpu seems to be v0.16.3
The text was updated successfully, but these errors were encountered: