I've upgraded my nvidia driver to 285.62 on a GTX 260 (Windows 7 x64) and now I have everthing broken. The first opengl error I see is an invalid operation on glVertexAttribPointer with a GL_FLOAT type.
I use a 3.3 forward compatible context attribs with core profile (tried without and give same error).
Reverting to the previous driver (275.33) everything gone fine again.
Does anyone have upgraded their nvidia driver to 285.62 and see any troubles ?
Try a debug context, it might print relevant info.
I'm using lwjgl-debug jar (2.8.2 #1434), and I have tried with a debug context.
No error before the invalid operation on glVertexAttribPointer (same with GL20.glVertexAttribPointer and ARBVertexProgram.glVertexAttribPointerARB).
With a null context (ie 2.x), the same code works fine (and it used to works fine too with the previous nvidia driver with opengl 3.x).
Anyone with an nvidia card and using 3.x ?
Is it possible that you are getting that error because of the following (taken from the OpenGL spec):
QuoteClient vertex arrays - all vertex array attribute pointers must refer to buffer
objects (section 2.9.2). The default vertex array object (the name zero) is
also deprecated. Calling VertexAttribPointer when no buffer object or no
vertex array object is bound will generate an INVALID OPERATION error,
as will calling any array drawing command when no vertex array object is
bound
I mean is it possible that NVidia is now enforcing the spec where it wasn't before?
Hum, seems we must exclusively use vao + vbo with 3.x.
Thanks for pointing me out this, I'll go read the spec about that.
So seems you're right, the new driver enforce the specs. Good in a way :)