cancel
Showing results for 
Search instead for 
Did you mean: 

OpenGL & Vulkan

Highlighted
Journeyman III
Journeyman III

ARB_shader_atomic_counters not in extension string; works anyway

ARB_shader_atomic_counters is not in the extension string, but when I use it it works anyway, partially anyway.

Getting the max_whatever_atomic_anything with glGetIntegerv always returns zero (that's the part that doesn't work). Creating and binding a buffer of type ATOMIC_COUNTER_BUFFER works fine, as does using atomic_uint in a shader. The results from using the atomic_counter are as expected (ie, the counter works, as far as I've tested it anyway, I'm not sure whether it actually works 100% correctly).

So it would appear that atomic counters work, but the driver wants to deny it, and it's bad at lying. What's going on here?

Related, the driver also denies being able to use GLSL 4.20, but shaders with #version 420 work fine.

GPU: HD6950
Catalyst: 11.9

Tags (1)
0 Kudos
Reply
2 Replies
Highlighted
Staff
Staff

ARB_shader_atomic_counters not in extension string; works anyway

Hi Harold,

Catalyst 11.9 doesn't officially support OpenGL 4.2 although some of the features may work anyway. That's why it doesn't advertise support. If you want a full implementation (with correct advertising), download the Catalyst beta with OpenGL 4.2 support from here:

http://support.amd.com/us/kbarticles/Pages/AMDCatalystOpenGL42BetaWin.aspx

Official support will follow shortly.

Graham

0 Kudos
Reply
Highlighted
Journeyman III
Journeyman III

ARB_shader_atomic_counters not in extension string; works anyway

Thanks, that makes sense, and I'll try the beta drivers.

0 Kudos
Reply