- August 25, 2009 at 8:08 pm #29903
It looks like with the latest SDK GL_OES_framebuffer_object and GL_OES_mapbuffer extensions are no longer working.
I had no problem accessing GL_OES_framebuffer_object under OGLES-1.1_WINDOWS_PCEMULATION_2.04.24.0811 but it appears to be missing with the latest SDK ( also confirmed by looking at the new console log )
Is it a bug or perhaps I need to enable something ?August 26, 2009 at 12:07 pm #33350
If you are running 2.5 SDK then it is likely that you can see PVRVFrame control window (small GUI), where you can toggle visiability of the Log. if this is so then please make log enable
and at beginning of it you can see (second line) , GL_RENDER string being displayed. The hardware profile should be mentioned there. eg.
RENDERER: PoverVR PVRVFrame 5.1 [hardware profile] ….
where hardware profile is : SGX530 , MBXLite, MBXLite with VGPLite etc.
OES_framebuffer is available for SGX530, SGX535 and generic profiles only . By default MBX with VGP is being set that do not support OES_framebuffer extension as well.
If that is a case then change the profile in General Options (menu command: Options->General) to one of the mentioned profiels that support that extension.
The list of supported extensions is also displayed in Log in forth line: EXTENSIONS:….
You can find more detailed description of how PVRVFrame Control Window in PVRVFrame Manual.
Tell us if this helped
jacekc 2009-08-26 12:07:45August 26, 2009 at 3:08 pm #33351
Thanks … it worked fine.
Quick question … reading thru the docs , it seems that the OES_mapbuffer extension doesn’t allow to read from the buffer and it can only be used for updates … is that correct ?