Sign in to follow this  
n00body

OpenGL Requesting list of useful extensions

Recommended Posts

I'm still learning my way around inside OpenGL, and trying to distill down the big list of extensions. Right now, I'm working with a 6800GT, affording me about 71 potential extensions (only counting ARB and EXT) in OpenGL 2.0.3. Can everyone make a list of extensions you find useful, or use a lot of the time? Also, could you give a brief description of what each does? On a side note, does anyone know which ones have been depreciated? For example, I'd heard GL_ARB_non_power_of_two is no longer needed since it's part of the core, but I'm not sure. Thanks for any help you can provide. ;)

Share this post


Link to post
Share on other sites
im only using one extension VBO ( at the most the number of extensions yould typically need u could count on your hand )
youll find if u use opengl2.0 (with glsl) a lot of the old extensions arent needed

Share this post


Link to post
Share on other sites
Some useful extensions:

Vertex Buffer Objects
Extension: GL_ARB_vertex_buffer_object
This was promoted to core in OpenGL 1.5.
This extension allows you to store your data (e.g. vertices, normals, texture coordinates) in a fast memory that is directly accessible to the GPU. This basically means that you can render much faster than you would be able to if the data was stored in system memory.
This is preferred method of storing data to be rendered nowadays. I haven't seen code which does not use VBO (except for very simple examples) in quite a while.

GLSL Shading Language
Extension: GL_ARB_shading_language_100
Promoted to core in Gl 2.0.
Presence of this extension determines if your hardware supports GLSL.

Extension: GL_ARB_shader_objects
Promoted to core in OpenGL 2.0.
This extension defines all entry points you need when working with GLSL shaders. It allows you to create, manage and use GLSL shaders.

Floating-Point Textures
Extension: GL_ARB_texture_float
As the name suggests, this allows you to create and use textures with floating-point data format (colour componetes can be 16 or 32 bit floats). This can be used when working with a lot of modern techniques like HDR, deferred rendering etc.
When using fp textures you will probably need GL_ARB_color_buffer_float which adds various pixel format options that control clamping of the colour components.

Rectangular and non-power-of-two textures
Extensions:
GL_ARB_texture_rectangle
GL_ARB_texture_non_power_of_two
These extensions alow you to use non-power-of-two textures that do not have to be square. NPOT extension was promoted to core in GL 2.0.

Multiple render targets
Extension: GL_ARB_draw_buffers
This was promoted to core in GL 2.0.
This extensions allows you to write output from your shaders to multiple outputs at once. For example, you can write colour of the pixel to one output and normal to another. Very useful for many advanced techniques.

Multitexturing
Extension: GL_ARB_multitexture
Promoted to core in OpenGL 1.3 (old :). This allows you to use multiple textures simultaneously (d'oh).

WGL Extensions List
Extension: WGL_ARB_extensions_string
Windows only. This extension allows you to query list of WGL extensions supported by your drivers and hardware. If you are using some sort of extension loader (e.g. GLEW), you will not need it.

Pixel Buffer Objects
Extension: WGL_ARB_pbuffer
Windows extension only. This allows you to create offscreen buffer to which you can output your rendering calls. Pixel buffer is basically an "invisible" equivalent of the window.

Render to texture
Extension: WGL_ARB_render_texture
Windows extension only. As the name suggests, this allows you to "redirect" your output to a texture. This texture can later be used just as any normal texture.

===========

Of course, this list is not exhaustive. All ARB extensions can be found in official extension registry. Newer extensions defined by NVIDIA can be found on a special page here. Similar page for ATI extensions can be found here.

Extensions that have been promoted to the core can be found at the end of the OpenGL specification. Newest specs can be found on this page.

Share this post


Link to post
Share on other sites
Thanks for the suggestions so far. I plan to use GL_EXT_frame_buffer_object because of all the good things I'd heard about it, and all the bad things I'd heard about pixel buffers.

One little question. If you have NPOT (particularly in GL2.0) then why do you need texture rectangle?

Share this post


Link to post
Share on other sites
Quote:
Original post by b2b3
Pixel Buffer Objects
Extension: WGL_ARB_pbuffer
Windows extension only. This allows you to create offscreen buffer to which you can output your rendering calls. Pixel buffer is basically an "invisible" equivalent of the window.


No, wrong.

WGL_ARB_pBuffer is for a pbuffer, this is NOT the same as a PBO or pixel buffer object.

PBOs are a method of performing Async transfers from the GPU and buffer to buffer copies on the GPU (such as textures to vertex buffers).

And frankly, unless you need a seperate context, you won't want to be using pbuffers, instead you want Frame Buffer Objects (FBO), which are the newer and much improved method of rendering to a texture.

There is also a short series of articles on FBOs written by some really top guy [grin]

Share this post


Link to post
Share on other sites
Okay, a couple more questions:
1.) What is sRGB, and why is it significant to OpenGL?

2.) PBOs. What is the most common use of them? Is there a place with a decent explanation? Are they to textures what VBOs are to geometry?

3.) How well supported is GL_EXT_texture_compression_s3tc across GPUs?

Share this post


Link to post
Share on other sites
I should probably look at sRGB at some point, however to answer the others;

2) PBOs are used for async copies of data to and from the graphics card (and from one buffer type to another). Textures already exist in video ram, PBOs just help with the uploading (so that the various functions don't block CPU execution).

3) The texture compression extensions have been supported for many generations now, I think even the orignal GeForce cards had support for it.

Share this post


Link to post
Share on other sites
Quote:

What is sRGB, and why is it significant to OpenGL?

sRGB is an ISO standarized non-linear colour space. In a normal RGB8 image, the colour distribution is completely linear. Each of the possible 255 increments is exactly the same over the entire dark to white range: 1/255.

However, the colour response of a display device (often being the final target for all OpenGL rendered content) is not linear. This is why usually gamma correction is applied on the final rendering.

A linear colour space such as RGB8 thus wastes a lot of values for brightness ranges the human eye cannot even distinguish due to the non-linearity of the screen, while lacking precision in other ranges. The solution would be to go to RGB16 or RGB16F, but this comes with a significant memory overhead.

The new sRGB formats try to find a middle ground. They distribute the dynamic ranges of the image in a way that matches the response curve of a screen more closely than plain RGB8. The net result is a higher quality of smooth gradients (ie. less banding) while the memory consumption stays the same.


[Edited by - Yann L on March 21, 2007 5:52:02 PM]

Share this post


Link to post
Share on other sites
Quote:
Original post by phantom
Quote:
Original post by b2b3
Pixel Buffer Objects
Extension: WGL_ARB_pbuffer
Windows extension only. This allows you to create offscreen buffer to which you can output your rendering calls. Pixel buffer is basically an "invisible" equivalent of the window.


No, wrong.

WGL_ARB_pBuffer is for a pbuffer, this is NOT the same as a PBO or pixel buffer object.

PBOs are a method of performing Async transfers from the GPU and buffer to buffer copies on the GPU (such as textures to vertex buffers).

And frankly, unless you need a seperate context, you won't want to be using pbuffers, instead you want Frame Buffer Objects (FBO), which are the newer and much improved method of rendering to a texture.

There is also a short series of articles on FBOs written by some really top guy [grin]


You are right, I got them mixed up [embarrass].

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Forum Statistics

    • Total Topics
      628277
    • Total Posts
      2981771
  • Similar Content

    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
    • By Abecederia
      So I've recently started learning some GLSL and now I'm toying with a POM shader. I'm trying to optimize it and notice that it starts having issues at high texture sizes, especially with self-shadowing.
      Now I know POM is expensive either way, but would pulling the heightmap out of the normalmap alpha channel and in it's own 8bit texture make doing all those dozens of texture fetches more cheap? Or is everything in the cache aligned to 32bit anyway? I haven't implemented texture compression yet, I think that would help? But regardless, should there be a performance boost from decoupling the heightmap? I could also keep it in a lower resolution than the normalmap if that would improve performance.
      Any help is much appreciated, please keep in mind I'm somewhat of a newbie. Thanks!
    • By test opty
      Hi,
      I'm trying to learn OpenGL through a website and have proceeded until this page of it. The output is a simple triangle. The problem is the complexity.
      I have read that page several times and tried to analyse the code but I haven't understood the code properly and completely yet. This is the code:
       
      #include <glad/glad.h> #include <GLFW/glfw3.h> #include <C:\Users\Abbasi\Desktop\std_lib_facilities_4.h> using namespace std; //****************************************************************************** void framebuffer_size_callback(GLFWwindow* window, int width, int height); void processInput(GLFWwindow *window); // settings const unsigned int SCR_WIDTH = 800; const unsigned int SCR_HEIGHT = 600; const char *vertexShaderSource = "#version 330 core\n" "layout (location = 0) in vec3 aPos;\n" "void main()\n" "{\n" " gl_Position = vec4(aPos.x, aPos.y, aPos.z, 1.0);\n" "}\0"; const char *fragmentShaderSource = "#version 330 core\n" "out vec4 FragColor;\n" "void main()\n" "{\n" " FragColor = vec4(1.0f, 0.5f, 0.2f, 1.0f);\n" "}\n\0"; //******************************* int main() { // glfw: initialize and configure // ------------------------------ glfwInit(); glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3); glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3); glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE); // glfw window creation GLFWwindow* window = glfwCreateWindow(SCR_WIDTH, SCR_HEIGHT, "My First Triangle", nullptr, nullptr); if (window == nullptr) { cout << "Failed to create GLFW window" << endl; glfwTerminate(); return -1; } glfwMakeContextCurrent(window); glfwSetFramebufferSizeCallback(window, framebuffer_size_callback); // glad: load all OpenGL function pointers if (!gladLoadGLLoader((GLADloadproc)glfwGetProcAddress)) { cout << "Failed to initialize GLAD" << endl; return -1; } // build and compile our shader program // vertex shader int vertexShader = glCreateShader(GL_VERTEX_SHADER); glShaderSource(vertexShader, 1, &vertexShaderSource, nullptr); glCompileShader(vertexShader); // check for shader compile errors int success; char infoLog[512]; glGetShaderiv(vertexShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(vertexShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::VERTEX::COMPILATION_FAILED\n" << infoLog << endl; } // fragment shader int fragmentShader = glCreateShader(GL_FRAGMENT_SHADER); glShaderSource(fragmentShader, 1, &fragmentShaderSource, nullptr); glCompileShader(fragmentShader); // check for shader compile errors glGetShaderiv(fragmentShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(fragmentShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::FRAGMENT::COMPILATION_FAILED\n" << infoLog << endl; } // link shaders int shaderProgram = glCreateProgram(); glAttachShader(shaderProgram, vertexShader); glAttachShader(shaderProgram, fragmentShader); glLinkProgram(shaderProgram); // check for linking errors glGetProgramiv(shaderProgram, GL_LINK_STATUS, &success); if (!success) { glGetProgramInfoLog(shaderProgram, 512, nullptr, infoLog); cout << "ERROR::SHADER::PROGRAM::LINKING_FAILED\n" << infoLog << endl; } glDeleteShader(vertexShader); glDeleteShader(fragmentShader); // set up vertex data (and buffer(s)) and configure vertex attributes float vertices[] = { -0.5f, -0.5f, 0.0f, // left 0.5f, -0.5f, 0.0f, // right 0.0f, 0.5f, 0.0f // top }; unsigned int VBO, VAO; glGenVertexArrays(1, &VAO); glGenBuffers(1, &VBO); // bind the Vertex Array Object first, then bind and set vertex buffer(s), //and then configure vertex attributes(s). glBindVertexArray(VAO); glBindBuffer(GL_ARRAY_BUFFER, VBO); glBufferData(GL_ARRAY_BUFFER, sizeof(vertices), vertices, GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 3 * sizeof(float), (void*)0); glEnableVertexAttribArray(0); // note that this is allowed, the call to glVertexAttribPointer registered VBO // as the vertex attribute's bound vertex buffer object so afterwards we can safely unbind glBindBuffer(GL_ARRAY_BUFFER, 0); // You can unbind the VAO afterwards so other VAO calls won't accidentally // modify this VAO, but this rarely happens. Modifying other // VAOs requires a call to glBindVertexArray anyways so we generally don't unbind // VAOs (nor VBOs) when it's not directly necessary. glBindVertexArray(0); // uncomment this call to draw in wireframe polygons. //glPolygonMode(GL_FRONT_AND_BACK, GL_LINE); // render loop while (!glfwWindowShouldClose(window)) { // input // ----- processInput(window); // render // ------ glClearColor(0.2f, 0.3f, 0.3f, 1.0f); glClear(GL_COLOR_BUFFER_BIT); // draw our first triangle glUseProgram(shaderProgram); glBindVertexArray(VAO); // seeing as we only have a single VAO there's no need to // bind it every time, but we'll do so to keep things a bit more organized glDrawArrays(GL_TRIANGLES, 0, 3); // glBindVertexArray(0); // no need to unbind it every time // glfw: swap buffers and poll IO events (keys pressed/released, mouse moved etc.) glfwSwapBuffers(window); glfwPollEvents(); } // optional: de-allocate all resources once they've outlived their purpose: glDeleteVertexArrays(1, &VAO); glDeleteBuffers(1, &VBO); // glfw: terminate, clearing all previously allocated GLFW resources. glfwTerminate(); return 0; } //************************************************** // process all input: query GLFW whether relevant keys are pressed/released // this frame and react accordingly void processInput(GLFWwindow *window) { if (glfwGetKey(window, GLFW_KEY_ESCAPE) == GLFW_PRESS) glfwSetWindowShouldClose(window, true); } //******************************************************************** // glfw: whenever the window size changed (by OS or user resize) this callback function executes void framebuffer_size_callback(GLFWwindow* window, int width, int height) { // make sure the viewport matches the new window dimensions; note that width and // height will be significantly larger than specified on retina displays. glViewport(0, 0, width, height); } As you see, about 200 lines of complicated code only for a simple triangle. 
      I don't know what parts are necessary for that output. And also, what the correct order of instructions for such an output or programs is, generally. That start point is too complex for a beginner of OpenGL like me and I don't know how to make the issue solved. What are your ideas please? What is the way to figure both the code and the whole program out correctly please?
      I wish I'd read a reference that would teach me OpenGL through a step-by-step method. 
  • Popular Now