Vertex Array Object (VAO) State Management in Core Profile

Defined behavior when modifying vertex attributes without an active VAO

In an OpenGL Core Profile context (GL 3.0+), calling glVertexAttribPointer (or any attribute‑state function) while no Vertex Array Object is bound – including the case where VAO 0 is bound – generates GL_INVALID_OPERATION. The attribute pointer call does not modify any state and the error is recorded.

Confirmed facts from the specification

• The Core Profile requires a VAO to be bound before any draw call (glDrawArrays/glDrawElements) and before any attribute‑state command that captures buffer bindings.
• VAO 0 is reserved as the default vertex array object, but the specification states that in a Core Profile the default object does not exist; binding it does not provide a valid state container.
• Only a non‑zero VAO name returned by glGenVertexArrays can store attribute enables, GL_ARRAY_BUFFER bindings, and (if used) GL_ELEMENT_ARRAY_BUFFER bindings.

Likely explanation / vendor behavior

Because VAO 0 does not capture state, some drivers may appear to accept the call and silently ignore it, while others will immediately raise the error. This inconsistency means that relying on VAO 0 as a fallback is not portable across hardware vendors.

Steps to set up vertex attributes correctly

1. Generate a VAO: GLuint vao; glGenVertexArrays(1, &vao);
2. Bind it: glBindVertexArray(vao);
3. Bind the VBO you want to use: glBindBuffer(GL_ARRAY_BUFFER, vbo);
4. Specify the attribute pointer: glVertexAttribPointer(index, size, type, normalized, stride, pointer);
5. Enable the attribute array: glEnableVertexAttribArray(index);
6. (Optional) Unbind the VAO: glBindVertexArray(0);
7. Before drawing, bind the VAO again: glBindVertexArray(vao); then issue draw calls.

Verification

After setup, query the bound VAO with glGetIntegerv(GL_VERTEX_ARRAY_BINDING, &bound); it should return the VAO you generated. Check for GL_INVALID_OPERATION after any attribute call if you suspect a missing VAO bind.