You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BAD_MATCH is generated if the EGL_CONTEXT_OPENGL_NO_ERROR_KHR is TRUE at
the same time as a debug or robustness context is specified.
It's illegal to request a context that is both "no errors" and "debug", however it's fine to have a "debug" context when "no errors" is supported but not enabled.
The text was updated successfully, but these errors were encountered:
bgK
changed the title
Unable to create debug context with EGL when ·KHR_create_context_no_error is supported
Unable to create debug context with EGL when KHR_create_context_no_error is supported
Oct 19, 2023
kchibisov
added a commit
to kchibisov/glutin
that referenced
this issue
Oct 19, 2023
The api/egl always disabled debug when `NO_ERROR` was present in
extensions to avoid errors, however the error will be thrown only
when using `NO_ERROR` and debug context at the same time.
Fix the same issues with GLX/WGL as well as properly enable `NO_ERROR`
for those backends.
Fixes: rust-windowing#1635
The api/egl always disabled debug when `NO_ERROR` was present in
extensions to avoid errors, however the error will be thrown only
when using `NO_ERROR` and debug context at the same time.
Fix the same issues with GLX/WGL as well as properly enable `NO_ERROR`
for those backends.
Fixes: #1635
When creating a context with EGL and the following code:
The debug bit does not get set on the GL context:
This seems to be caused by this check:
glutin/glutin/src/api/egl/context.rs
Line 108 in e75330f
The spec for
KHR_create_context_no_error
mentions an interaction with debug contexts:It's illegal to request a context that is both "no errors" and "debug", however it's fine to have a "debug" context when "no errors" is supported but not enabled.
The text was updated successfully, but these errors were encountered: