Oops forgot to CC the list.
On 10-10-14 09:41 AM, Alejandro Segovia wrote:Is the error a "null function error"? Or something more exotic? Null
> Hello List,
> I'm using PyOpenGL for conducting a Computer Graphics course at the
> University where I work.
> One of my students is working on an Intel-based card (on W/Vista) that
> reports OpenGL version 1.5, however, when trying to create VBO's, he
> was getting an error from deep inside the wrapper. I figured this was
> probably because of the function wrapper existing, but not being
> actually linked to anything, which would imply VBO's are not supported
> by his driver.
function error is basically just PyOpenGL saying "that doesn't exist"
when you go to call the function. If the function evaluates to true
(i.e. bool( fun ) == True), then we may have an error in the wrappers.
>Normally you wouldn't use the raw version, but rather the
> The solution was to use the vertex_buffer_object ARB extension, which
> had to be imported using something akin to:
> >>from OpenGL.raw.GL.ARB.vertex_buffer_object import *
OpenGL.GL.ARB.vertex_buffer_object version. VBOs, in particular, are
actually provided as a wrapper (OpenGL.arrays.vbo), but this is the
general pattern of use.
> I was wondering, is this the recommended way to import and useI seem to recall them being core in 1.5, yes.
> extensions in PyOpenGL? and, is it possible that although the Intel
> driver reports OpenGL version 1.5, it does not provide VBO's? I
> thought VBO's were promoted to Core in version 1.5.