kas1e
Daniel says that not warp3d, not ogles2 know about GL_QUADS, so he think that maybe gl4es' quad -> triangle conversion is somehow broken. Maybe something big-endian related in that conversion...
> Do you have the same effect with LIBGL_BEGINEND=0 ? No differences, the same > Also, another simple test to do, is to simply swap GL_QUADS with GL_TRIANGLE_FAN because there...
I may forget something, but should it just print stuff to console then? In my case now, does not matter if I do ```setenv LIBGL_LOGSHADERERROR 1```, or if I do...
It doesn't sounds very much like usual shader error yes, but it still bring erros about shaders can't be compiled :) I need to check where those words placed are....
You are right, it seems it come from Irrlicht itself, but then why only now and what is that .. Why not before .. Maybe because before we use some...
It probabaly come from ```source/Irrlicht/COpenGLShaderMaterialRenderer.cpp```
Nope, doing "setenv LIBGL_ARBPROGRAM 1" didn't help, still bring this error.
Yeah, that it! Damn, I was sure it was already in gl4es as if I remember right you work on something of that sort? Or it was a plan ?:)
I change the title of the topic to be more understandable, so once a time (if) will come, it will be not forgotten :) But currently ```setenv LIBGL__NOARBPROGRAM 1" did...
By the way, checked file buffers.c and there is such a block: ``` //ARB wrapper #ifndef AMIGAOS4 void glGenBuffersARB(GLsizei n, GLuint * buffers) AliasExport("gl4es_glGenBuffers"); void glBindBufferARB(GLenum target, GLuint buffer) AliasExport("gl4es_glBindBuffer");...