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
The application allows the user to specify core context (which also seems to force "forward compatibility" even though it's not the same thing) versus "default", whatever that means for the driver.
There is no way to force "compatibility" context, no control over "forward compatibility" flag and no way to specify minimal OpenGL version.
For example, on my HD7850 most applications report OpenGL version 4.5, because that's what the driver gives when not asked for any specific version (which according to spec is the same as asking for 1.0) so I though 4.5 is all I have.
But I recently found out that asking for 4.6 during context creation actually succeeds. I would like to be able to examine this 4.6 context but there is currently no way of doing so.
The text was updated successfully, but these errors were encountered:
Can you elaborate? I haven't done much with OpenGL since Vulkan was released, and I don't have any AMD hardware to test this on. So I either need some more details, or you could do a pull request that changes this behavior.
The application allows the user to specify core context (which also seems to force "forward compatibility" even though it's not the same thing) versus "default", whatever that means for the driver.
There is no way to force "compatibility" context, no control over "forward compatibility" flag and no way to specify minimal OpenGL version.
For example, on my HD7850 most applications report OpenGL version 4.5, because that's what the driver gives when not asked for any specific version (which according to spec is the same as asking for 1.0) so I though 4.5 is all I have.
But I recently found out that asking for 4.6 during context creation actually succeeds. I would like to be able to examine this 4.6 context but there is currently no way of doing so.
The text was updated successfully, but these errors were encountered: