-
Notifications
You must be signed in to change notification settings - Fork 35
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
Support opengl 3.3 #163
Comments
Thank you for filing! |
Here is the output from those commands: glxinfo: I do have other computers and I can use Neovim however it'd be nice if Zed/blade worked on this laptop as well. I didn't realize it would take a lot of work. I also tried Zed with Vulkan but unfortunately its unusable with lavapipe. |
I took another look at the code. It doesn't seem as bad. Something isn't right here, though, it should be working right away.
This is an error from Naga, and it reports Naga backend capabilities. On Blade side we have a similarly named capabilities.set(
super::Capabilities::BUFFER_STORAGE,
extensions.contains("GL_EXT_buffer_storage"),
); This should make our Naga configuration to use GLES-3.20 version: let force_explicit_bindings = self
.capabilities
.contains(super::Capabilities::BUFFER_STORAGE);
let mut naga_options = glsl::Options {
version: glsl::Version::Embedded {
version: if force_explicit_bindings { 320 } else { 300 },
is_webgl: cfg!(target_arch = "wasm32"),
},
writer_flags: extra_flags | glsl::WriterFlags::ADJUST_COORDINATE_SPACE,
binding_map: Default::default(),
zero_initialize_workgroup_memory: false,
}; And that should unlock both features that the error is talking about on Naga side: check_feature!(BUFFER_STORAGE, 400, 310);
check_feature!(DYNAMIC_ARRAY_SIZE, 430, 310); I wonder if you'd be interested in running this through |
Alright, I'll try debugging it further. Also, I just ran the blade bunnymark demo with GLES and it worked fine 🤔 |
I have a older thinkpad and I cannot run the Zed editor because blade requires newer opengl features (BUFFER_STORAGE and DYNAMIC_ARRAY_SIZE)... Is there any chance these can be made optional?
The text was updated successfully, but these errors were encountered: