KhronosGroup / KhronosGroup/OpenGL-Refpages
glVertexAttribPointer() assumes non-default VAO
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 492
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
Description
The following text is misleading, because it assumes non-default VAO is bound, and makes it impossible to figure out how to use client side data (compatibility profile).
If pointer is not NULL, a non-zero named buffer object must be bound to the GL_ARRAY_BUFFER target (see glBindBuffer), otherwise an error is generated. pointer is treated as a byte offset into the buffer object's data store. The buffer object binding (GL_ARRAY_BUFFER_BINDING) is saved as generic vertex attribute array state (GL_VERTEX_ATTRIB_ARRAY_BUFFER_BINDING) for index index.
I understand that this is only for legacy use, but IMHO also the compatibility profile should be covered by the reference pages.
Even the specification itself is a bit confusing, because it gives impression that using null pointer is somehow allowed. I suppose null pointer is allowed only so that it is possible to restore default GL state (and to make the default GL state "valid", even though you cannot use the null pointer).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the glVertexAttribPointer reference-page text quoted in the issue and compare it with the OpenGL specification's compatibility-profile behavior. Clarify how client-side pointers and null pointers should be described, and consider the work done when the reference page no longer implies that a non-default VAO is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- computer-graphics, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100