-
Notifications
You must be signed in to change notification settings - Fork 33
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
Fallback to glow when wgpu fails #42
Comments
looking at the code it does not look like this is supported. I tried to make it fallback but the AppCreator is moved and I'm not able to retry with a new backend. I will need to ponder on how to do this properly. |
eframe has no built-in rendering fallback, no. Instead of falling back on @Wumpf probably has some smart ideas related to that. |
eframe would need quite a bit of refactor to make a runtime decision about There's some important fixes in wgpu 0.20 (will update egui soon!) regarding corner cases of backend selection when a backend is available but the surface is not compatible (should never happen but window managers can be weird on Linux...). I'm ofc also very curious how wgpu fails, did you report a bug (please do!)? Is it a known issue? |
@Wumpf Here's the log, it fails on my intel graphics laptop on linux (nixos):
|
this is 0.72.2
|
looks like wgpu figured it can't use Vulkan (it fails creating an adapter), then tried to pick OpenGL and rejected that as well because it didn't fit the minspec - unfortunately doesn't say what about it isn't sufficient 🤔 . The fact that it couldn't use Vulkan hints at outdated drivers usually. Which is strange because it also mentions Mesa 23.3.5 for OpenGL which is quite new. Can you try telling wgpu to either use vulkan or gl by setting only the respective backends on egui's render config? There's a bug in wgpu 0.19 that sometimes has issues when the first backend in the list doesn't work out (fixed in wgpu 0.20) and this sounds a little bit like that. |
On Tue, Apr 30, 2024 at 07:00:19AM GMT, Andreas Reich wrote:
looks like wgpu figured it can't use Vulkan (it fails creating an adapter), then tried to pick OpenGL and rejected that as well because it didn't fit the minspec - unfortunately doesn't say what about it isn't sufficient 🤔 . The fact that it couldn't use Vulkan hints at outdated drivers usually. Which is strange because it also mentions Mesa 23.3.5 for OpenGL which is quite new.
Can you try telling wgpu to either use vulkan or gl by setting only the respective backends on egui's render config? There's a bug in wgpu 0.19 that sometimes has issues when the first backend in the list doesn't work out (fixed in wgpu 0.20) and this sounds a little bit like that.
Alternatively, you can also try with egui master branch - wgpu was updated there a few hours ago
ok will do, thanks! will report back.
|
There are some wgpu issues that are fixed in egui-master, so let's switch to that. This fixes notedeck so that it runs on both my intel graphics laptop and amdgpu desktop. Fixes: #28 Fixes: #42 Fixes: #141 Signed-off-by: William Casarin <[email protected]>
@Wumpf this does appear to fix it! thanks! |
There are some wgpu issues that are fixed in egui-master, so let's switch to that. This fixes notedeck so that it runs on both my intel graphics laptop and amdgpu desktop. Fixes: #28 Fixes: #42 Fixes: #141 Signed-off-by: William Casarin <[email protected]>
For some reason when the wgpu backend fails it just halts instead of switching to glow. We need to figure out if this is a bug in eframe (@emilk), if this is something we're doing wrong, or if this is even supported.
The text was updated successfully, but these errors were encountered: