-
Notifications
You must be signed in to change notification settings - Fork 28
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
Failure to create core context on Intel Sandybridge with Mesa #4
Comments
Thanks for your bug report. I have successfully queried a OpenGL core context on Linux with Mesa: GLFW is working properly. I also had problems when it came to getting a core context. There was always a popup window warning about context creation failure (which gave a very useful error message: "Context profiles are only defined for OpenGL version 3.2 and above", See: http://imgur.com/xwswYKSl.png), but there's a workaround (which is not a fix, it's a workaround). The real reason for this bug resides on the following lines of the file "glCapsViewer.cpp"
If you change lines 409 and 410 to:
You'll get a core context under Linux. The command "glxinfo" outputs this on my computer: (...) Pay attention that there is no core context that targets OpenGL 3.0 (although there is a compability one). I've also visited the OpenGL's wiki about that: But the code seems to be following the guidelines there, so there isn't a definitively fix yet (and maybe there will never be one. Maybe this is an issue with Mesa refusing to ship core contexts before the breakage point, which is OpenGL 3.2. The error message the popup window gave hinted that way). |
I have created a pull request that should fix the issue: |
On my Intel Sandybridge GPU, glCapsViewer fails to read the OpenGL Core Profile properties. GLFW reports that a Core Profile context is only available with OpenGL 3.2+. However, I am able to create a Core Profile context with version 3.3 from Qt using QSurfaceFormat and QOpenGLContext. Also, glxinfo also states that version 3.3 should be possible for Core:
Not so, however, for non-core:
I suspect that this might in fact be a GLFW bug.
The text was updated successfully, but these errors were encountered: