You get the benefit of higher potential performance, but you do have to be careful. This isn’t Python or even PASCAL where there are “guard rails” to avoid the programmer shooting themselves in the foot. Reason is you’d often provide a “NULL pointer” in this case to indicate 0 offset into the bound VBO.īut if a VBO isn’t bound properly, it just ends up being a NULL CPU pointer which you’d expect to generate the above error.Įrrant pointers passed into the driver can easily crash the driver. You’d expect to see this if you are “trying” to render with VBOs, but you don’t happen to have a VBO bound to the GL_ARRAY_BUFFER when you register a vertex attribute or don’t have a VBO bound to the GL_ELEMENT_ARRAY_BUFFER when you issue the draw call. Often what this means is that you have provided a bogus client array pointer for a vertex attribute or the index list. Looks like a null pointer dereference to me. …Access violation reading location 0x00000000.
0 kommentar(er)
