I am also using glGenBuffers and stuff, but glGenVertexArray and co. are supposed to allow to save the states of the vertex so I have not to call glVertexPointer and other vertex array related function for every frame.

Another thing, with glBindBuffer(), if I use a constant like the one defined in the documentation, python doesn't know it, I have to postfix them with _ARB?

Below is an example:

glBindBuffer(GL_ARRAY_BUFFER_ARB, self.buffers[0])

Could it be that with my hardware this is an extension?



Le 07/15/10 17:56, Alejandro Segovia a écrit :
Hi Roland,

I don't know precisely about those specific 3.0 functions, but in my code I'm using glGenBuffers, glBindBuffer and glBufferData to populate my VBO's (PyOpenGL version 3.0.1b). I think these are core in OpenGL 2.0.


On Thu, Jul 15, 2010 at 10:37 AM, Roland Everaert <r.everaert@gmail.com> wrote:

I am currently trying to use VBOs, but it seems that pyOpenGL 3.0.1 is
lacking the functions glGenVertexArrays(), glBindVertexArray() and I
suppose glDeleteVertexArray().

Below is the error I get:

NameError: global name 'glGenVertexArrays' is not defined

According to the OpenGL Programming Guide (the red book) seventh edition
and some document I found on the official site of OpenGL, those
functions exists since OpenGL 3.0.

The basic question is, does pyOpenGL 3.0.1 belongs to OpenGL 3.0 or not?

If yes, could it be related to the implementation for my platform or my
graphics hardware?

If not, to which version of OpenGL does pyOpenGL 3.0.1 belongs?



This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
PyOpenGL Homepage
PyOpenGL-Users mailing list

Alejandro Segovia Azapian
Director, Algorithmia: Visualization & Acceleration