Open MarcoMeijer opened 1 week ago
Based on the logged system info, their drivers seem ancient (circa 2016).
I am not sure what Bevy's expected support for hardware that old is (see #14078, there's no official policy), but I would recommend that the user try updating their drivers if possible.
I think the general attitude is that we leave these issues open because someone who cares could decide to work on this, but this isn't a priority for bevy maintainers.
Maybe an acceptable, generalized solution would be to not unwrap()
results like this? It's not outlandish for an error to be returned, so our function should handle that case.
You/your play-tester could try the wgpu examples (https://github.com/gfx-rs/wgpu/tree/trunk/examples), and eventually open an issue there, because it should generally work, and not result in a lost device error. (especially when Desktop GL is used)
I don't know if we can do any better than "file a warning that explicitly says to update your graphics drivers". If we can't get a render device, we can't run a graphical application / game.
That said, maybe wgpu should handle these older devices / drivers more gracefully?
Bevy version
Bevy 0.15-rc.3
Relevant system information
What you did
Made a very simple bevy app (spawn a sprite and press f to toggle fullscreen).
What went wrong
Bevy crashed immediately on the computer of a play tester. It didn't crash on 0.14.2. Also it works normally on my pc (also windows 10, and I send the .exe to the playtester).
Additional information
It crashes on line 363 in the file bevy_render/src/renderer/mod.rs. This is the line that crashes: