Skip to content
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

glscopeclient requires GL 4.2 even though we don't need most 4.2 features #212

Closed
azonenberg opened this issue Oct 5, 2020 · 6 comments
Closed
Labels
rendering Changes to display capabilities tabled Plans for the future. Not ready to write code yet.

Comments

@azonenberg
Copy link
Collaborator

We can probably get away with GL 3.x as long as we have GL_ARB_compute_shader and GL_ARB_gpu_shader_int64. This might allow running in VMWare?

@azonenberg azonenberg added the rendering Changes to display capabilities label Oct 5, 2020
@azonenberg azonenberg changed the title glscopeclient requires GL 4.3 even though we don't need most 4.3 features glscopeclient requires GL 4.2 even though we don't need most 4.2 features Oct 5, 2020
@azonenberg
Copy link
Collaborator Author

Minimum requirement is now 4.2 plus a bunch of extensions. It looks like glBindImageTexture is the main thing we need from 4.2, can we go even further down with extension checks or finding another way to do this?

@nshcat
Copy link
Collaborator

nshcat commented Oct 5, 2020

The question is whether the set of GPUs that happen to both support the extensions and at the same time not OpenGL 4.2 is sufficiently large to make it worth the effort. Do we have any data on this?

@azonenberg
Copy link
Collaborator Author

The immediate use case is WSL. Here's a glxinfo dump:

https://gist.github.com/bluecmd/e2c5bd22a5fa70a1e32541a2e5540c49

It reports OpenGL 3.3 core profile plus, AFAIK, all of the extensions we need.

@azonenberg
Copy link
Collaborator Author

As far as VMware goes, it looks like Workstation 15 will not work (it's missing compute shaders among other extensions), but if we can get down to 4.1 plus extensions there's a good chance that Workstation 16 will work. I might upgrade my Workstation license to 16 soon since it seems like the list of GL extensions it supports is hard to find.

Haven't looked at other hypervisors yet.

@xzcvczx
Copy link
Contributor

xzcvczx commented Apr 24, 2021

Intel Ivy Bridge also supports compute shaders with recent versions of mesa on Linux. however I needed to use

MESA_GL_VERSION_OVERRIDE=4.3 MESA_GLSL_VERSION_OVERRIDE=430

in order for it not to error out

@azonenberg azonenberg added this to the v0.1 milestone Apr 24, 2021
azonenberg added a commit that referenced this issue Apr 24, 2021
…3.0, allowing us to run on some OpenGL 4.2 implementations such as Mesa on Ivy Bridge integrated graphics. See #212.
@azonenberg azonenberg removed this from the v0.1 milestone Apr 28, 2021
@azonenberg azonenberg added the tabled Plans for the future. Not ready to write code yet. label Apr 28, 2021
@azonenberg
Copy link
Collaborator Author

Closing as wontfix now that the long term plan is to transition everything to Vulkan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rendering Changes to display capabilities tabled Plans for the future. Not ready to write code yet.
Projects
None yet
Development

No branches or pull requests

3 participants