Hi Godmil, My apologies for this. Our plan had been to get a load of documentation done over December so that people grabbing Chimera had a good starting point for it. If you drop me an email to support@zerodependency.co.uk, I will send over a simple test project that you can use to get started befo...

I'm happy for you to send me emails/PM's with any questions. I've been programming with OpenGL for about 8 years now, and OpenGL ES for about 18 months.

I'm not familiar with glDiscardFramebufferEXT() myself, but it appears you're trying to discard the native framebuffer? Surely this isn't valid behaviour?

Just as a word of advice, be very careful about timing specific GL calls - it is entirely up to the driver to decide when to implement the tasks you've given it. So you could easily have 5 calls saying only 1ms timing, but then have the 6th saying 20ms simply because that's when the driver decides t...

The reason why the vc_* functions are not better documented, I believe, is because most of those functions are proprietary Broadcom calls, with no released source or documentation - until that changes I don't see decent documentation being put together.

Never mind!

All sorted!

Thanks again

Thanks! That did indeed to the trick. Now I have a separate problem that it goes all through the config code, and my render code (currently just calling glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT); however it never renders to the framebuffer, I stay at commandline with my std::cout logging be...

That'd be a no

Thanks, I'll give that a try

Hi all, I've just started developing on the Pi, and I'm using the hello_triangle as a basis for setting up my OpenGL ES program. I get as far as creating an EGL Context (and eglGetError() returns EGL_SUCCESS) - but on the next line I'm calling graphics_get_display_size, and it's returning a value of...