Sorry, there isn't a way round it other than, as you said, to not use vertex array objects and instead rely on core GL.

So my OpenGL ES port seems to be complete now without further issues. For completeness I'll list the problems I came across: - No GL_OES_vertex_array_object extension - No GL_OES_depth_texture extension - glEnableVertexAttribArray should not be called if the attribute does not exist in the shader (e...

So I got to the bottom of my issue. In the renderer we loop round all the possible vertex attributes that a model has and call glEnableVertexAttribArray and glVertexAttribPointer using the location from the currently bound shader. However some of the shaders don't use all the attributes and it turns...

What's stranger is that if I render 2 of the 5 attribute models then neither show (however both of them show after rendering the 7 attribute model). My thoughts are that there is something about the render path of the 7 attribute model that leaves OpenGL in a state that allows it to then render the ...

I'm trying to port a game engine to Raspberry Pi 3. The engine supports iOS and Android (running OpenGL ES 2.0) and Windows (running standard OpenGL). I've added a RPi backend to the engine that runs OpenGL ES 2.0 and for the most part everything is fine (UI and sprites render), however I've got one...