Repository navigation
glGetVertexArrayIndexediv() missing VERTEX_ATTRIB_BINDING #675
Description
GetVertexAttrib*() exposes queries to currently bound vertex array, to these properties:
VERTEX_ATTRIB_ARRAY_BUFFER_BINDINGVERTEX_ATTRIB_ARRAY_ENABLEDVERTEX_ATTRIB_ARRAY_SIZEVERTEX_ATTRIB_ARRAY_STRIDEVERTEX_ATTRIB_ARRAY_TYPEVERTEX_ATTRIB_ARRAY_NORMALIZEDVERTEX_ATTRIB_ARRAY_INTEGERVERTEX_ATTRIB_ARRAY_LONGVERTEX_ATTRIB_ARRAY_DIVISORVERTEX_ATTRIB_BINDINGVERTEX_ATTRIB_RELATIVE_OFFSETCURRENT_VERTEX_ATTRIB
Meanwhile GetVertexArrayIndexed() provides query to specific vertex array without needing to bind it to make the query. However, the list of queriable properties appears to be missing VERTEX_ATTRIB_BINDING:
VERTEX_ATTRIB_ARRAY_BUFFER_BINDINGVERTEX_ATTRIB_ARRAY_ENABLEDVERTEX_ATTRIB_ARRAY_SIZEVERTEX_ATTRIB_ARRAY_STRIDEVERTEX_ATTRIB_ARRAY_TYPEVERTEX_ATTRIB_ARRAY_NORMALIZEDVERTEX_ATTRIB_ARRAY_INTEGERVERTEX_ATTRIB_ARRAY_LONGVERTEX_ATTRIB_ARRAY_DIVISORVERTEX_ATTRIB_RELATIVE_OFFSETVERTEX_BINDING_STRIDEVERTEX_BINDING_DIVISORVERTEX_BINDING_BUFFER
What happened to VERTEX_ATTRIB_BINDING?
It looks like at least MESA driver supports GetVertexArrayIndexed(VERTEX_ATTRIB_BINDING) query, but not some other drivers.
Activity
tksuoran commentedon Jan 29, 2026
Original extension https://registry.khronos.org/OpenGL/extensions/ARB/ARB_direct_state_access.txt has this:
So I think the intention was to allow
VERTEX_ATTRIB_BINDINGforGetVertexArrayIndexediv(). But this was not mentioned in " For GetVertexArrayIndexediv, must be one of" part of the extension. Also, the core spec state tables don't seem to mention DSA functions.I am guessing that by accident, the DSA extension only mentioned VERTEX_ATTRIB_BINDING for Table 23.4, and because of that, when DSA was added to core, and state tables left out the DSA functions, the VERTEX_ATTRIB_BINDING was not carried to the core by accident.
Another question is, if I use GetVertexArrayIndexediv via the extension, I should be able to query VERTEX_ATTRIB_BINDING, right?