raylectron crashes nvidia opengl drivers

The drivers must be doing some kind of pre-flight check, and that’s causing the access violation. But here’s the interesting part: The IDs aren’t hooked up to any attributes in the shader code. I’ve got some enables that are leaking to shaders where no AttribPointer call is made – because – as it always is – I was getting a bit too aggressive with the optimizations. It has to do with glEnableVertexAttribArray and glVertexAttribPointer. Should crash right away if you have a PC/nVidia setup.Īs always, the minute I post this, I think I’ve found the problem, but will need to verify with my users, hopefully by tomorrow. You can find the latest PC build at the url above.

The shader compile correctly, and all the locations have proper integers. Has anybody encountered this? Is there a way to get further debug information? I’m sure it’s something simple the PC nVidia drivers are doing differently, maybe they require things to be set in a certain order?įurther notes: No built-in variables are used, all vertex, uv, matrixes, etc, are passed in by vertex arrays or uniforms. Sadly, I don’t have this configuration, and debug code to my users isn’t getting me anywhere. On nVidia, it always crashes, the first shader call (against a glDrawArrays), with pretty much any shader, no matter how simple. It works on iOS (es2), OS X with Intel GPU, nVidia, or ATI(AMD) cards, and on the PC with ATI(AMD) or Intel GPU. The editor is all fixed function, it works everywhere. I’m the author of an open source, cross-platform freeware 3D engine dim3 ( Two components: the engine and the editor.

Raylectron crashes nvidia opengl drivers