PDA

View Full Version : Regarding GL_EXT_framebuffer_object



myk45
03-26-2012, 11:05 PM
Hello,

I queried for all OpenGL extensions using glGetString(GL_EXTENSIONS). And GL_EXT_framebuffer_object is listed as one of them. Now, isn't this a part of the core profile after OpenGL 3.0?

The GL version i have is 3.3.0, as reported by glGetString(GL_VERSION). So, why is FBO still reported as an extension?

I have an nVidia 8400 GS.

Thanks.

Alfonse Reinheart
03-26-2012, 11:18 PM
Because that's just how they do it. Many implementations will offer up old extension versions of core functionality, so that applications written against the extension won't break. It also allows you to code for hardware that doesn't support the core version, even though your hardware does.

myk45
03-26-2012, 11:32 PM
Hmm, interesting. Thanks for the reply. So, it could be that some implementation by another hardware vendor may not support the functionality as an extension, wherein the query would fail?(but functionality still exists).

menzel
03-27-2012, 12:54 AM
Hello myk45,

you can find a rough overview of which extension became a core feature when here: http://www.opengl.org/wiki/History_of_OpenGL .

Yes, e.g. a 3.2 core implementation for example might not return the extension string GL_EXT_framebuffer_object but support the functionality as it became core in 3.0 (hint: a well known fruit-named computer brand...).

myk45
03-27-2012, 02:30 AM
Hi menzel,

Thanks for the link!

>> (hint: a well known fruit-named computer brand...)
haha ;)

overlay
03-27-2012, 12:50 PM
Note that GL_ARB_framebuffer_object is a core extension of GL3.0, not GL_EXT_framebuffer_object.

Both extensions differ slightly. This is an exert of the "Overview" section of GL_ARB_framebuffer_object, explaining the difference:

http://www.opengl.org/registry/specs/ARB/framebuffer_object.txt

"This extension differs from EXT_framebuffer_object by splitting the framebuffer object binding point into separate DRAW and READ bindings (incorporating functionality introduced by EXT_framebuffer_blit). This allows copying directly from one framebuffer to another. In addition, a new high performance blit function is added to facilitate these blits and perform some data conversion where allowed."

BionicBytes
03-28-2012, 12:13 AM
adding to the discussion of EXT vs ARB differences is that the ARB version allows a mixture of texture formats and sizes but the EXT does not.
My understanding is that if you have a GL 3.x context then you definately have ARB like functionality regardless of the GL_EXT extension string being advertised by the implmentation. The only reason for the vendor still showing EXT in the extensions strings is to continue to allow older progs to function correctly as they propably explicitly test for the extension to be present and make use of it when they find it.