Sign in to follow this  
iNsAn1tY

OpenGL Depth texture + FBO = problem...

Recommended Posts

Hi, I'm trying to attach a 16-bit depth texture to an FBO, but I keep getting GL_FRAMEBUFFER_UNSUPPORTED_EXT for the FBO status. The depth texture is created with the following parameters: internalformat = GL_DEPTH_COMPONENT16 format = GL_DEPTH_COMPONENT type = GL_UNSIGNED_INT There's another texture already attached as the first colour attachment, which has the following parameters: internalformat = GL_RGBA8 format = GL_RGBA type = GL_UNSIGNED_BYTE Neither of the textures cause any OpenGL errors when they're created. Am I doing something silly like using the wrong type, or is this something deeper? I'd like to not have to hack my way round this problem, so if anyone can shed any light on it, I'll be very thankful... PS. My card is an NVIDIA Geforce 7800, with the latest 93.71 drivers.

Share this post


Link to post
Share on other sites
A little more on this. I dug out a program I wrote last year which used FBOs. I wrote the code below, creating a 24-bit depth render buffer, and it works just fine. Is it just perhaps that a depth texture is unacceptable?

glGenFramebuffersEXT(1, &lFbo);
glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, lFbo);

glGenRenderbuffersEXT(1, &lRb);
glBindRenderbufferEXT(GL_RENDERBUFFER_EXT, lRb);

glRenderbufferStorageEXT(GL_RENDERBUFFER_EXT, GL_DEPTH_COMPONENT24, 1024, 1024);
glFramebufferRenderbufferEXT(GL_FRAMEBUFFER_EXT, GL_DEPTH_ATTACHMENT_EXT, GL_RENDERBUFFER_EXT, lRb);

Share this post


Link to post
Share on other sites
I think it's because nvidia only allows the same depth as the main frame buffer at the moment, be careful though as ATi cards unless they added support for 24bit, only work with 16bit depth in FBOs to make it extra confusing.

Share this post


Link to post
Share on other sites
You know you don't need a renderbuffer for a depth map?

What about GL_CLAMP_TO_EDGE for textures? I thought I remember FBO's in some cases need that set... But I could be wrong. I use GL_FLOAT for my types, but don't think that matters either.

I would ditch the RB if you don't need it. I know that 16bit works cause I have used it myself with a RB before.

Share this post


Link to post
Share on other sites
Quote:
Original post by BiGCyC
I think it's because nvidia only allows the same depth as the main frame buffer at the moment, be careful though as ATi cards unless they added support for 24bit, only work with 16bit depth in FBOs to make it extra confusing.


Recent drivers seem to support the depth_stencil extension so in theory at least 24bit depth is supported on ATI cards now, along with 8bit stencil...

(in practise; I'm not tried it yet and I don't know of anyone how has.. maybe tomorrow/later today... )

Share this post


Link to post
Share on other sites
Quote:
Original post by MARS_999
You know you don't need a renderbuffer for a depth map?

What about GL_CLAMP_TO_EDGE for textures? I thought I remember FBO's in some cases need that set... But I could be wrong. I use GL_FLOAT for my types, but don't think that matters either.

I would ditch the RB if you don't need it. I know that 16bit works cause I have used it myself with a RB before.

Yeah, I know the render buffer works. The point I was making with my second post was that while the render buffer works, a depth texture doesn't, which is puzzling (not mention deeply annoying).

GL_CLAMP_TO_EDGE is set when I use the texture by CgFX, but I can't see why it should affect rendering to the texture. I changed to using GL_FLOAT, which made no difference, unfortunately.

Quote:
Original post by BiGCyC
I think it's because nvidia only allows the same depth as the main frame buffer at the moment, be careful though as ATi cards unless they added support for 24bit, only work with 16bit depth in FBOs to make it extra confusing.

Not sure what bit-depth of depth buffer I'm using; the system is running through a GLUT testbed application, so I guess it could be anything...the program that uses the render buffer actually acquires its RC through Win32, so I know for a fact it's using a 32-bit depth there...perhaps I'll move everything over to Win32 (which is planned anyway, shouldn't take long), and see if that makes any difference...

Share this post


Link to post
Share on other sites
Quote:
Original post by iNsAn1tY
Quote:
Original post by BiGCyC
I think it's because nvidia only allows the same depth as the main frame buffer at the moment, be careful though as ATi cards unless they added support for 24bit, only work with 16bit depth in FBOs to make it extra confusing.

Not sure what bit-depth of depth buffer I'm using; the system is running through a GLUT testbed application, so I guess it could be anything...the program that uses the render buffer actually acquires its RC through Win32, so I know for a fact it's using a 32-bit depth there...perhaps I'll move everything over to Win32 (which is planned anyway, shouldn't take long), and see if that makes any difference...

Turns out it was this. I switched over to using Win32 with a 32-bit depth buffer, and it seems to be working now. Thanks for the replies.

Share this post


Link to post
Share on other sites
Quote:
Original post by iNsAn1tY
Quote:
Original post by iNsAn1tY
Quote:
Original post by BiGCyC
I think it's because nvidia only allows the same depth as the main frame buffer at the moment, be careful though as ATi cards unless they added support for 24bit, only work with 16bit depth in FBOs to make it extra confusing.

Not sure what bit-depth of depth buffer I'm using; the system is running through a GLUT testbed application, so I guess it could be anything...the program that uses the render buffer actually acquires its RC through Win32, so I know for a fact it's using a 32-bit depth there...perhaps I'll move everything over to Win32 (which is planned anyway, shouldn't take long), and see if that makes any difference...

Turns out it was this. I switched over to using Win32 with a 32-bit depth buffer, and it seems to be working now. Thanks for the replies.

Oh. It wasn't that. A bug was causing a different FBO problem, and when I resolved that, this one came back.

If you're rendering to a depth texture (not a render buffer, an actual texture) using an FBO on similar NVIDIA hardware (Geforce 7800 GTX), could you post here?

Share this post


Link to post
Share on other sites
Hi, I'm messing with shadow mapping just now so have some code handy if it helps.

As you can see, I just use GL_DEPTH_COMPONENT as the texture format, so I take it that the current depth buffer setting is used (mine is 24-bit).

The code shows the essentials for creating/freeing everything and how to bind the fbo for rendering. You Probably don't need all of this but I hope some of it helps you, and others..


//-------------------------------------
//create the depth texture - only once
//-------------------------------------
glEnable(GL_TEXTURE_2D);
glGenTextures(1, @DepthTexture);
glBindTexture(GL_TEXTURE_2D, texture);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR);
glTexEnvi(GL_TEXTURE_ENV, GL_TEXTURE_ENV_MODE, GL_MODULATE);
glCopyTexImage2d(GL_TEXTURE_2D, 0, GL_DEPTH_COMPONENT, 0, 0, aWidth, aHeight, 0);
glBindTexture(GL_TEXTURE_2D, 0);
glDisable(GL_TEXTURE_2D);

//-------------------------------------
//init fbo with depth texture - only once
//-------------------------------------
glGenFramebuffersEXT(1, @fbo);
glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, fbo);
glFramebufferTexture2DEXT(GL_FRAMEBUFFER_EXT,
GL_DEPTH_ATTACHMENT_EXT, GL_TEXTURE_2D, DepthTexture, 0);
glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, 0);

//-------------------------------------
//bind the fbo for rendering - every frame
//-------------------------------------
glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, fbo);
glDrawBuffer(GL_NONE);
glReadBuffer(GL_NONE);

//-------------------------------------
//set up viewport etc. and Draw stuff - every frame
//-------------------------------------
Dorender();

//-------------------------------------
//unbind the fbo - every frame
//-------------------------------------
glBindFramebufferEXT(GL_FRAMEBUFFER_EXT, 0);

//-------------------------------------
//delete the fbo and depth texture - only once
//-------------------------------------
glDeleteFramebuffersEXT(1, @fbo);
glDeleteTextures(1, @DepthTexture);

Share this post


Link to post
Share on other sites
Quote:
Turns out it was this. I switched over to using Win32 with a 32-bit depth buffer, and it seems to be working now. Thanks for the replies

no nvidia cards support 32bit depths

to sumerize with nvidia cards

if u do color + depth (eg fbo) the depth needs to be the same as the mainwindow (normally 24bit) thus 16bit will fail
but if u need depth only (eg shadowmap) then u can use either 16 or 24bit

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  

  • Announcements

  • Forum Statistics

    • Total Topics
      628320
    • Total Posts
      2982057
  • 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