Crash on Windows (probably old graphics card)

[ModProg]

The executable run is the cushy theme example.

PS C:\Users\ModProg\Downloads> .\theme.exe
thread '<unnamed>' panicked at /home/modprog/.cargo/git/checkouts/kludgine-da36743fea3cc9cc/3ee472a/src/app.rs:898:10:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

WGPU issue: https://github.com/gfx-rs/wgpu/issues/5164

[ecton]

As per investigations in a conversation on Discord, the target card is an Nvidia 840M. In my searching, I found gpuweb/gpuweb#1069, which as of the time of writing this comment seems to imply that the webgpu spec thinks this card is the minimum DX12 target. I can't seem to find specific information about wgpu's DX12 requirements.

Regardless, wgpu has removed its DX11 backend in favor of its OpenGL implementation. This is supposed to be used for compatibility on devices that don't support the required DX12 feature level or shader model. Unfortunately, the APIs to request an adapter simply return an Option. I have no extra information to report about why wgpu doesn't think it can initialize an adapter.

I think the next step is to try running a wgpu example on the device in question. If the wgpu examples fail, then perhaps a report to wgpu to investigate why this card isn't supported. If the wgpu examples work, then I might file my own report because I believe the only feature I'm using is supposed to be emulated on backends that don't provide the feature natively.

[alexniver]

same issue on my old archlinux laptop.

wgpu version: 0.19.1

device info:

AdapterInfo { name: "AMD Radeon R5 M435 (RADV HAINAN)", vendor: 4098, device: 26213, device_type: DiscreteGpu, driver: "radv", driver_info: "Mesa 23.3.5-arch1.1", backend: Vulkan }

wgpu 0.18 no issue

[ecton]

@alexniver, are you able to reproduce this problem using wgpu's examples? If so, reporting this to wgpu would be helpful. Since ModProg's original issue was relating to Windows' support for older GPUs, it seems like a separate issue for wgpu's maintainers to investigate would be helpful.

[ModProg]

it seems like a separate issue for wgpu's maintainers to investigate would be helpful.

Especially because I never created mine :sweat_smile:

[ecton]

it seems like a separate issue for wgpu's maintainers to investigate would be helpful.

Especially because I never created mine 😅

I'm so confused -- the description of the issue links to an issue you created a few weeks ago :)

[ModProg]

it seems like a separate issue for wgpu's maintainers to investigate would be helpful.

Especially because I never created mine 😅

I'm so confused -- the description of the issue links to an issue you created a few weeks ago :)

you are right, I should buy a new brain