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
{{ message }}
This repository has been archived by the owner on Mar 9, 2024. It is now read-only.
nvidia had this thing where each fixed-function attribute mapped to an index in the hardware.
However, as generic binding of vertex attributes by index was started, this overlapped.
glVertexAttribPointerARB(3, ..) should actally be an alias for glColorPointer
I'm not sure how GLSL handles this, it seems to work fine for attribute 0 as gl_Position, but that might just be luck?
Unfortunately, doing this the other way around (mapping old-attributes to custom ones) would require emulation of the fixed function pipeline or duplicate uploads (to custom attributes and the fixed-function ones).
So to resolve this, glVertexAttribPointerARB should always alias, except for weights (probably).
A better solution can be implemented later.
The text was updated successfully, but these errors were encountered:
Migrated from original GitLab issue 72
nvidia had this thing where each fixed-function attribute mapped to an index in the hardware.
However, as generic binding of vertex attributes by index was started, this overlapped.
See https://www.khronos.org/registry/OpenGL/extensions/NV/NV_vertex_program.txt (2.14.1.6 Semantic Meaning for Vertex Attributes and Program Parameters)
glVertexAttribPointerARB(3, ..)
should actally be an alias for glColorPointerI'm not sure how GLSL handles this, it seems to work fine for attribute 0 as gl_Position, but that might just be luck?
Unfortunately, doing this the other way around (mapping old-attributes to custom ones) would require emulation of the fixed function pipeline or duplicate uploads (to custom attributes and the fixed-function ones).
So to resolve this,
glVertexAttribPointerARB
should always alias, except for weights (probably).A better solution can be implemented later.
The text was updated successfully, but these errors were encountered: