-
Notifications
You must be signed in to change notification settings - Fork 31
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
GLES panic on Intel Gen7 #155
Comments
Yeah, it's very weird that your Mesa's GLES implementation is behind. I see no reason why it can't support the shader storage buffers. |
I did some more digging. First off, here's the output when running in debug mode with logging enabled:
The panic seems to happen here, so the error originates inside naga. Indeed, A few questions here: Is blade supposed to be working with GLSL version 300? AFAIK version 310 is only enabled for hardware that fully supports GLES 3.1, which would mean that the GLES backend requires GLES 3.1. Or does it all depend on the user of blade and what shaders they use? I tried to run the bunnymark and particle demos in WebGL mode but they didn't run (bunnymark was a runtime panic and the particle demo didn't even compile). Are they working for you? |
I just noticed that the bunnymark example actually runs on my hardware with GLES, so I guess the problem here is that the particle example uses features in its shaders that are not supported by GLES 3.0. |
Yes, Blade supports GLES-3.0 because that matches WebGL2. You just can't use any storage buffers on that platform. |
I'm trying to run blade on an Intel HD Graphics 4000 (Gen7, Ivy Bridge). When I run it using Vulkan with the following command everything seems to work:
even though I get the following warning:
However, if I try to run it with GLES using the following command, it panics:
I'm using Ubuntu 24.04 with Mesa 24.0.9 on Wayland.
eglinfo
vulkaninfo
I'm guessing the problem here is that my hardware only supports GLES 3.0 but blade requires GLES 3.1. I'm assuming it's the missing GL_ARB_shader_storage_buffer_object extension, which interestingly is supported on my machine when using desktop GL but not when using GLES. Might this be a Mesa bug?
Given that my hardware is able to run the Vulkan version and GLES is supposed to be a fallback, it would be great if the GLES version would work as well.
The text was updated successfully, but these errors were encountered: