-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
Migrate to OpenGL Core Profile #864
Comments
It seems like GLEW is no longer a great solution.
I'd be in favor of using |
The OpenGL wiki also has a full list:
|
This should also solve #567 |
This issue has been mentioned on Avogadro Discussion. There might be relevant details there: |
Hi @ghutchis I understand the issue now. Do you have a specific version of OpenGL in mind for our migration? If we're considering implementing geometry shaders, we might need to update the OpenGL version. Could you clarify our exact plans regarding this? Also we need to keep make sure that changing to a "modern" version doesn't result in any issues for the users??? |
We had discussed at least OpenGL 3.2 core, but you can see that was ~2 years ago, so we might be able to set on OpenGL 4.0 core. I think the main thing would be to check baseline support, but probably 4.0 / 4.1 is fine. |
I'll mention that beyond 4.1 is problematic because Apple doesn't support more recent OpenGL on Mac. (Which is a shame, because compute shaders would be nice for some features.) |
Oh , I didn't know that. Thanks for quickly addressing my questions. |
I know very little about graphics stacks and assume that moving to Vulkan, and VulkanVK on macOS, is not a trivial thing but rather a ridiculous amount of work? |
Yes. Vulkan is not something I'd want to pursue at this point. OpenGL 4.0 / 4.1 are well supported and likely to continue because of WebGL needs in browsers. |
This issue has been mentioned on Avogadro Discussion. There might be relevant details there: |
It would be great to move to the OpenGL core profile. At the moment @cryos has started this .. I'm adding this issue to track.
The text was updated successfully, but these errors were encountered: