Sign in to follow this  
ZaiPpA

OpenGL How does OpenGL create its depth values?

Recommended Posts

ZaiPpA    122
Hi. I was under the impression, from reading some articles/books, that OpenGL calculated its depth values like this: (let's look at a vertex, for simplicity)
vec4 clipspaceVertex = projectionMatrix * modelViewMatrix * gl_Vertex;
float depth = clipspaceVertex.z / clipspaceVertex.w * 0.5 + 0.5;
I.e. calculate the clip-space coordinate, perform the perspective division (which makes -1 <= z <= 1), scale and bias the z-value (so that 0 <= z <= 1) and use this final z-value as the depth. But when i try this, the depth value doesn't seem right. I'm probably missing something. How do i calculate the depth-value? (given a point in clipspace) Thanx for your help! (yeah, i know i could get the depth of a fragment with gl_FragCoord.z in a fragment program, but i'm not actually interested in the depth from the cameras point of view, but rather from the point of view of a lightsource)

Share this post


Link to post
Share on other sites
ZaiPpA    122
Thanx for the links. Just to follow up: (in case it can help someone else)

I tried looking at the perspective matrix from DirectX (see [1], if you have the book). After the matrix multiplication and the division by w (done on paper), i got the same expression for the depth as in "Learning to love your Z buffer". (it seems like he assumes that w=1 before the multiplication with the projection matrix - which is ok by me) (and that he assumes DirectX - not ok by me)

Looking at the OpenGL-matrix (again, see [1]), i of course get another expression for the depth. If i plug in z=znear into the expression, i get depth = -1 and if i plug in z=zfar i get depth = 1. (for DirectX i get 0 and 1)


So it seems that DirectX has clipcoords in the range: (for points not outside the frustum)
(x,y,z,1) = [-1;1]x[-1;1]x[0;1]x{1}
while OpenGL has clipcoords in the range: (for points not outside the frustum)
(x,y,z,1) = [-1;1]x[-1;1]x[-1;1]x{1}

But depth values are in [0;1], so in OpenGL the clip z-coord has to be scaled/biased to get into [0;1] instead of [-1;1] i guess (as i wrote in the first post).

So it seems to me that my way of calculating the depth in the first post was correct. Or?
(probably something else is wrong in my code)

[1] Möller and Haines: "Real-time rendering", page 65.

Share this post


Link to post
Share on other sites
V-man    813
Quote:
But depth values are in [0;1], so in OpenGL the clip z-coord has to be scaled/biased to get into [0;1] instead of [-1;1] i guess (as i wrote in the first post).

Yes that is correct. glDepthRange controls that and by default it is set as glDepthRange(0.0, 1.0)
This is a function that is not available in D3D.

Share this post


Link to post
Share on other sites
godmodder    828
typedef struct D3DVIEWPORT9 {
DWORD X;
DWORD Y;
DWORD Width;
DWORD Height;
float MinZ;
float MaxZ;
} D3DVIEWPORT9, *LPD3DVIEWPORT9;

I'm not an expert in Direct3D (mostly use OpenGL), but I believe the MinZ and MaxZ are the values that set the depth range in D3D.

Jeroen

Share this post


Link to post
Share on other sites
kRogue    100
Some corrections:

In OpenGL for the depth values there are 2 co-ordinates systems:
1) normalized device co-ordinates, this is _ALWAYS_ -1 to 1.
2) window co-ordinates, this is _ALWAYS_ 0 to 1.

now, glDepthRange(near,far) sets the transformation from device co-ordinates to window co-ordinates, as the linear mapping so that T(-1)=near and T(1)=far, thus glDepthRange(0,1) uses the full range of the depth buffer, and glDepthRange(0,0.5) would only use half of it's prescision (since -1-->0 and 1-->0.5) The actual stored value is the window co-ordinate, typically as a 24bit fixed point value.



on a unix system type man glDepthRange to see more.

Share this post


Link to post
Share on other sites
SnotBob    202
OpenGL spec is your friend. Check out Section 2.11 in glspec15:
zw = [(f-n)/2]zd + (n+f)/2 , where
n and f are by default 0 and 1, so
zw = 0.5 * zd + 0.5, where zd = zc/wc
zw is then converted to the integer range of the depth buffer.

Seeing that you got the transformation right, how exactly don't the values seem right?

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  

  • Similar Content

    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
    • By markshaw001
      Hi i am new to this forum  i wanted to ask for help from all of you i want to generate real time terrain using a 32 bit heightmap i am good at c++ and have started learning Opengl as i am very interested in making landscapes in opengl i have looked around the internet for help about this topic but i am not getting the hang of the concepts and what they are doing can some here suggests me some good resources for making terrain engine please for example like tutorials,books etc so that i can understand the whole concept of terrain generation.
       
    • By KarimIO
      Hey guys. I'm trying to get my application to work on my Nvidia GTX 970 desktop. It currently works on my Intel HD 3000 laptop, but on the desktop, every bind textures specifically from framebuffers, I get half a second of lag. This is done 4 times as I have three RGBA textures and one depth 32F buffer. I tried to use debugging software for the first time - RenderDoc only shows SwapBuffers() and no OGL calls, while Nvidia Nsight crashes upon execution, so neither are helpful. Without binding it runs regularly. This does not happen with non-framebuffer binds.
      GLFramebuffer::GLFramebuffer(FramebufferCreateInfo createInfo) { glGenFramebuffers(1, &fbo); glBindFramebuffer(GL_FRAMEBUFFER, fbo); textures = new GLuint[createInfo.numColorTargets]; glGenTextures(createInfo.numColorTargets, textures); GLenum *DrawBuffers = new GLenum[createInfo.numColorTargets]; for (uint32_t i = 0; i < createInfo.numColorTargets; i++) { glBindTexture(GL_TEXTURE_2D, textures[i]); GLint internalFormat; GLenum format; TranslateFormats(createInfo.colorFormats[i], format, internalFormat); // returns GL_RGBA and GL_RGBA glTexImage2D(GL_TEXTURE_2D, 0, internalFormat, createInfo.width, createInfo.height, 0, format, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); DrawBuffers[i] = GL_COLOR_ATTACHMENT0 + i; glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + i, textures[i], 0); } if (createInfo.depthFormat != FORMAT_DEPTH_NONE) { GLenum depthFormat; switch (createInfo.depthFormat) { case FORMAT_DEPTH_16: depthFormat = GL_DEPTH_COMPONENT16; break; case FORMAT_DEPTH_24: depthFormat = GL_DEPTH_COMPONENT24; break; case FORMAT_DEPTH_32: depthFormat = GL_DEPTH_COMPONENT32; break; case FORMAT_DEPTH_24_STENCIL_8: depthFormat = GL_DEPTH24_STENCIL8; break; case FORMAT_DEPTH_32_STENCIL_8: depthFormat = GL_DEPTH32F_STENCIL8; break; } glGenTextures(1, &depthrenderbuffer); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); glTexImage2D(GL_TEXTURE_2D, 0, depthFormat, createInfo.width, createInfo.height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, depthrenderbuffer, 0); } if (createInfo.numColorTargets > 0) glDrawBuffers(createInfo.numColorTargets, DrawBuffers); else glDrawBuffer(GL_NONE); if (glCheckFramebufferStatus(GL_FRAMEBUFFER) != GL_FRAMEBUFFER_COMPLETE) std::cout << "Framebuffer Incomplete\n"; glBindFramebuffer(GL_FRAMEBUFFER, 0); width = createInfo.width; height = createInfo.height; } // ... // FBO Creation FramebufferCreateInfo gbufferCI; gbufferCI.colorFormats = gbufferCFs.data(); gbufferCI.depthFormat = FORMAT_DEPTH_32; gbufferCI.numColorTargets = gbufferCFs.size(); gbufferCI.width = engine.settings.resolutionX; gbufferCI.height = engine.settings.resolutionY; gbufferCI.renderPass = nullptr; gbuffer = graphicsWrapper->CreateFramebuffer(gbufferCI); // Bind glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo); // Draw here... // Bind to textures glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, textures[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, textures[1]); glActiveTexture(GL_TEXTURE2); glBindTexture(GL_TEXTURE_2D, textures[2]); glActiveTexture(GL_TEXTURE3); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); Here is an extract of my code. I can't think of anything else to include. I've really been butting my head into a wall trying to think of a reason but I can think of none and all my research yields nothing. Thanks in advance!
    • By Adrianensis
      Hi everyone, I've shared my 2D Game Engine source code. It's the result of 4 years working on it (and I still continue improving features ) and I want to share with the community. You can see some videos on youtube and some demo gifs on my twitter account.
      This Engine has been developed as End-of-Degree Project and it is coded in Javascript, WebGL and GLSL. The engine is written from scratch.
      This is not a professional engine but it's for learning purposes, so anyone can review the code an learn basis about graphics, physics or game engine architecture. Source code on this GitHub repository.
      I'm available for a good conversation about Game Engine / Graphics Programming
  • Popular Now