• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
rubenhak

OpenGL
Position Reconstruction from Depth in OpenGL

8 posts in this topic

Hi Everybody,

I'm in a long journey of implementing deferred shading. I've got a clear idea of the algorithm, but have some troubles reconstructing object position. I've followed this article [url="http://mynameismjp.wordpress.com/2009/03/10/reconstructing-position-from-depth/"]http://mynameismjp.wordpress.com/2009/03/10/reconstructing-position-from-depth/[/url] but still easily get lots. There are too many uncertainties. So I want to go over it step by step and make that I did not make any mistakes in previous steps.


Storing the depth into a texture:

[CODE]
// Depth Pass Vertex Shader

varying float depth;
void main (void)
{
gl_Position = gl_ProjectionMatrix * gl_ModelViewMatrix * gl_Vertex;
vec4 pos = gl_ModelViewMatrix * gl_Vertex;
depth = pos.z;
}
[/CODE]

[CODE]
// Depth Pass Fragment Shader
varying float depth;
uniform float FarClipPlane;
void main (void)
{
float d = - depth / FarClipPlane;
gl_FragColor.r = d;
}
[/CODE]

My understanding of this is that I do store the liner depth value into the texture. Is that correct?

Thank you,
Ruben


Also, I'm easily getting lost when it gets to the perspective division. Can somebody suggest some article where i can learn about it.
0

Share this post


Link to post
Share on other sites
Yes, this is correct, but you should move the division into the vertex shader.
[CODE]
varying float depth;
uniform float FarClipPlane;
void main (void)
{
gl_Position = gl_ProjectionMatrix * gl_ModelViewMatrix * gl_Vertex;
vec4 pos = gl_ModelViewMatrix * gl_Vertex;
depth = -pos.z / FarClipPlane;
}

// Depth Pass Fragment Shader
varying float depth;
void main (void)
{
gl_FragColor.r = depth;
}
[/CODE]
And remember, that holding the depth in a single component of 8bit or 16bit will introduce artifacts.
1

Share this post


Link to post
Share on other sites
[quote name='rubenhak' timestamp='1336513950' post='4938494']
Hi Everybody,

I'm in a long journey of implementing deferred shading. I've got a clear idea of the algorithm, but have some troubles reconstructing object position. I've followed this article [url="http://mynameismjp.wordpress.com/2009/03/10/reconstructing-position-from-depth/"]http://mynameismjp.w...ion-from-depth/[/url] but still easily get lots. There are too many uncertainties. So I want to go over it step by step and make that I did not make any mistakes in previous steps.


Storing the depth into a texture:

[CODE]
// Depth Pass Vertex Shader

varying float depth;
void main (void)
{
gl_Position = gl_ProjectionMatrix * gl_ModelViewMatrix * gl_Vertex;
vec4 pos = gl_ModelViewMatrix * gl_Vertex;
depth = pos.z;
}
[/CODE]

[CODE]
// Depth Pass Fragment Shader
varying float depth;
uniform float FarClipPlane;
void main (void)
{
float d = - depth / FarClipPlane;
gl_FragColor.r = d;
}
[/CODE]

My understanding of this is that I do store the liner depth value into the texture. Is that correct?

Thank you,
Ruben


Also, I'm easily getting lost when it gets to the perspective division. Can somebody suggest some article where i can learn about it.
[/quote]

Ashaman73 is correct, however you seem to be having trouble with the theory itself.
before reading take a look at this:
http://mynameismjp.wordpress.com/2010/09/05/position-from-depth-3/
namely method #2

Ok so you store the depth like this:
[CODE]
[vertex shader]

varying float depth;
const float far_plane_distance = 1000.0f; //far plane is at -1000

[...]

//transform the input vertex to view (or eye) space
vec4 viewspace_position = modelview_matrix * input_vertex;

//this is not perspective division but scaling the depth value.
//initially you'd have depth values in the range [-near ... -far distance]
//but you have to linearize them, so that you can get more
//precision
//this is why you divide by the far plane distance
//and you divide by the negative one, so that you can
//check the result in the texture
depth = viewspace_position.z / -far_plane_distance;

[pixel shader]

varying float depth;
out vec4 out_depth;

[...]

//store the depth into the R channel of the texture
//assuming you chose a R16F or R31F format
out_depth.x = depth;

[/CODE]

and retrieve (decode) the depth like this:
[CODE]
[vertex shader]

varying vec4 viewspace_position;
varying vec2 texture_coordinates;

[...]

//store the view space position of the far plane
//this gets interpolated as you could see in the mjp drawing
viewspace_position = modelview_matrix * input_vertex;
texture_coordinates = input_texture_coordinates;

[pixel shader]

varying vec4 viewspace_position;
varying vec2 texture_coordinates;
uniform sampler2D depth_texture;
const float far_plane_distance = 1000.0f;

[...]

//sample depth from the texture's R channel
//this will be in range [0 ... 1]
float linear_depth = texture(depth_texture, texture_coordinates).x;

//you have to construct the view vector at the extrapolated viewspace position
//and scale it by the far / z, but this is unnecessary if you use the far plane as the input viewspace position
//since the division will give you 1
//the z coordinate will be the far distance (negative, since we're in viewspace)
vec3 view_vector = vec3(viewspace_position.xy * (-far_plane_distance / viewspace_position.z), -far_plane_distance);

//scaling the view vector with the linear depth will give the true viewspace position
vec3 reconstructed_viewspace_position = view_vector * linear_depth;

[/CODE]

hope this helped :) I had trouble with reconstructing position so search for it on gamedev.
1

Share this post


Link to post
Share on other sites
[quote name='Ashaman73' timestamp='1336550949' post='4938605']
Yes, this is correct, but you should move the division into the vertex shader.
[/quote]
Could you please explain what would be the difference of doing that in a vertex vs pixel shaders. Except the performance difference, aren't the numbers supposed to be same?

[quote name='Ashaman73' timestamp='1336550949' post='4938605']
And remember, that holding the depth in a single component of 8bit or 16bit will introduce artifacts.
[/quote]
I will try to encode it into 3 or 4 8bit components. You already gave the idea how to do that in another thread.
0

Share this post


Link to post
Share on other sites
[quote name='Yours3!f' timestamp='1336564479' post='4938643']
Ashaman73 is correct, however you seem to be having trouble with the theory itself.
before reading take a look at this:
[url="http://mynameismjp.wordpress.com/2010/09/05/position-from-depth-3/"]http://mynameismjp.w...n-from-depth-3/[/url]
namely method #2

Ok so you store the depth like this:

hope this helped [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img] I had trouble with reconstructing position so search for it on gamedev.
[/quote]

I've read those lots of times but its very hard to understand the entire thing at once. I need to do it step-by-step.
Yours3!f, in one of the methods in the article frustum corner positions are used to reconstruct the position. I guess
it was used for world space position reconstruction, and you're reconstructing into view space, right?

So, if I go with the same approach, how should I perform lighting calculation? What would be the positions
of the camera and lights. Also regarding the normals, should that be translated? My understand is that in
view space:
[CODE]
camera_position_view_space = [0, 0, 0];
light_position_view_space = view_matrix * light_position_world_space;
light_direction_view_space = view_matrix * light_direction_world_space;
normal_view_space = normalize(view_matrix * normal_world_space);
[/CODE]

Ashaman73, Yours3!f, you guys help me a lot with this! I need some time to digest it.
0

Share this post


Link to post
Share on other sites
[quote name='rubenhak' timestamp='1336585651' post='4938714']
[quote name='Yours3!f' timestamp='1336564479' post='4938643']
Ashaman73 is correct, however you seem to be having trouble with the theory itself.
before reading take a look at this:
[url="http://mynameismjp.wordpress.com/2010/09/05/position-from-depth-3/"]http://mynameismjp.w...n-from-depth-3/[/url]
namely method #2

Ok so you store the depth like this:

hope this helped [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img] I had trouble with reconstructing position so search for it on gamedev.
[/quote]

I've read those lots of times but its very hard to understand the entire thing at once. I need to do it step-by-step.
Yours3!f, in one of the methods in the article frustum corner positions are used to reconstruct the position. I guess
it was used for world space position reconstruction, and you're reconstructing into view space, right?

So, if I go with the same approach, how should I perform lighting calculation? What would be the positions
of the camera and lights. Also regarding the normals, should that be translated? My understand is that in
view space:
[CODE]
camera_position_view_space = [0, 0, 0];
light_position_view_space = view_matrix * light_position_world_space;
light_direction_view_space = view_matrix * light_direction_world_space;
normal_view_space = normalize(view_matrix * normal_world_space);
[/CODE]

Ashaman73, Yours3!f, you guys help me a lot with this! I need some time to digest it.
[/quote]

yep I describe the frustum corner method. I made it work in view space, but mjp describes a world space method as well. (so I guess the frustum one doesn't work in worldspace)
The lighting calculation is independent from what space you're using. Or at least I've seen lighting in world space, view space, tangent space... The basic thing is that you have to be consistent. If you're performing lighting in view space then you need to transform everything into view space. Normals, position, light position are the needed parameters. You should also read the lighthouse3d articles about lighting. If you wanna go the deferred way then I think viewspace suits your needs best.
To you viewspace, you just have to export your meshes to object space. The you can use your modelview matrix to transform them instantly into view space, and then the projection matrix to transform them to projection space.

for the normals you need to use a so called "normal matrix". This matrix is either the upper left 3x3 part of your view matrix, or the transpose of the inverse of your modelview matrix. You probably want to do this on the cpu side. In glsl:
[CODE]
mat3 normal_matrix_1 = mat3(view_matrix);

mat3 normal_matrix_2 = mat3(transpose(inverse(modelview_matrix)));
[/CODE] Edited by Yours3!f
0

Share this post


Link to post
Share on other sites
[quote name='Yours3!f' timestamp='1336662686' post='4939004']
yep I describe the frustum corner method. I made it work in view space, but mjp describes a world space method as well. (so I guess the frustum one doesn't work in worldspace)
[/quote]
OMG!! I didn't know those were your articles! Those are awesome! I honestly take my hat off for you!

Just want to confirm with you that with your method#2 I'd not need to deal with frustum corners, right? Multiplication of view_vector and linear_depth would give me reconstructed position in the view space.

Also, could you suggest some article where I can learn more about view/projection spaces in order to get a better idea how it works and why is the depth projected into [-far, -near] range.

Thank you!
Ruben
0

Share this post


Link to post
Share on other sites
[quote name='rubenhak' timestamp='1336669784' post='4939048']
[quote name='Yours3!f' timestamp='1336662686' post='4939004']
yep I describe the frustum corner method. I made it work in view space, but mjp describes a world space method as well. (so I guess the frustum one doesn't work in worldspace)
[/quote]
OMG!! I didn't know those were your articles! Those are awesome! I honestly take my hat off for you!

Just want to confirm with you that with your method#2 I'd not need to deal with frustum corners, right? Multiplication of view_vector and linear_depth would give me reconstructed position in the view space.

Also, could you suggest some article where I can learn more about view/projection spaces in order to get a better idea how it works and why is the depth projected into [-far, -near] range.

Thank you!
Ruben
[/quote]

ummm... I think you misunderstood me. That is not my article. I just implemented it. That article belongs to MJP: [url="http://www.gamedev.net/user/118414-mjp/"]http://www.gamedev.n...ser/118414-mjp/[/url]

you DO have to deal with it. That is the basis of the reconstruction. If you read the mjp article #3 (back in the habit) then you'll understand it. View vector is actually constructed from the coordinates of the far plane of the view frustum, that were interpolated along the whole screen.

just a couple of articles:
[url="http://www.songho.ca/opengl/gl_transform.html"]http://www.songho.ca..._transform.html[/url]
[url="http://www.songho.ca/opengl/gl_projectionmatrix.html"]http://www.songho.ca...tionmatrix.html[/url]
[url="http://www.songho.ca/math/homogeneous/homogeneous.html"]http://www.songho.ca...omogeneous.html[/url]
[url="http://www.glprogramming.com/red/chapter03.html"]http://www.glprogram.../chapter03.html[/url]
[url="http://www.glprogramming.com/red/"]http://www.glprogramming.com/red/[/url] ---> this is a whole book (although it is for OGL 1.1, some parts are still relevant like the article above)

this is an awesome book about the maths behind all this:
[url="http://www.amazon.com/Primer-Graphics-Development-Wordware-Library/dp/1556229119"]http://www.amazon.co...y/dp/1556229119[/url]
despite it describes maths in a left-handed coordinate system, I'm sure that after reading this you'll be able to apply it in the OpenGL world, the right-handed cooridnate system. Edited by Yours3!f
1

Share this post


Link to post
Share on other sites
Yours3!f, thank you so much for this! I really appreciate.
I need few days to digest and try it out. I will get back to this thread with my results!
0

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  
Followers 0

  • Similar Content

    • By Solid_Spy
      Hello, I have been working on SH Irradiance map rendering, and I have been using a GLSL pixel shader to render SH irradiance to 2D irradiance maps for my static objects. I already have it working with 9 3D textures so far for the first 9 SH functions.
      In my GLSL shader, I have to send in 9 SH Coefficient 3D Texures that use RGBA8 as a pixel format. RGB being used for the coefficients for red, green, and blue, and the A for checking if the voxel is in use (for the 3D texture solidification shader to prevent bleeding).
      My problem is, I want to knock this number of textures down to something like 4 or 5. Getting even lower would be a godsend. This is because I eventually plan on adding more SH Coefficient 3D Textures for other parts of the game map (such as inside rooms, as opposed to the outside), to circumvent irradiance probe bleeding between rooms separated by walls. I don't want to reach the 32 texture limit too soon. Also, I figure that it would be a LOT faster.
      Is there a way I could, say, store 2 sets of SH Coefficients for 2 SH functions inside a texture with RGBA16 pixels? If so, how would I extract them from inside GLSL? Let me know if you have any suggestions ^^.
    • By KarimIO
      EDIT: I thought this was restricted to Attribute-Created GL contexts, but it isn't, so I rewrote the post.
      Hey guys, whenever I call SwapBuffers(hDC), I get a crash, and I get a "Too many posts were made to a semaphore." from Windows as I call SwapBuffers. What could be the cause of this?
      Update: No crash occurs if I don't draw, just clear and swap.
      static PIXELFORMATDESCRIPTOR pfd = // pfd Tells Windows How We Want Things To Be { sizeof(PIXELFORMATDESCRIPTOR), // Size Of This Pixel Format Descriptor 1, // Version Number PFD_DRAW_TO_WINDOW | // Format Must Support Window PFD_SUPPORT_OPENGL | // Format Must Support OpenGL PFD_DOUBLEBUFFER, // Must Support Double Buffering PFD_TYPE_RGBA, // Request An RGBA Format 32, // Select Our Color Depth 0, 0, 0, 0, 0, 0, // Color Bits Ignored 0, // No Alpha Buffer 0, // Shift Bit Ignored 0, // No Accumulation Buffer 0, 0, 0, 0, // Accumulation Bits Ignored 24, // 24Bit Z-Buffer (Depth Buffer) 0, // No Stencil Buffer 0, // No Auxiliary Buffer PFD_MAIN_PLANE, // Main Drawing Layer 0, // Reserved 0, 0, 0 // Layer Masks Ignored }; if (!(hDC = GetDC(windowHandle))) return false; unsigned int PixelFormat; if (!(PixelFormat = ChoosePixelFormat(hDC, &pfd))) return false; if (!SetPixelFormat(hDC, PixelFormat, &pfd)) return false; hRC = wglCreateContext(hDC); if (!hRC) { std::cout << "wglCreateContext Failed!\n"; return false; } if (wglMakeCurrent(hDC, hRC) == NULL) { std::cout << "Make Context Current Second Failed!\n"; return false; } ... // OGL Buffer Initialization glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT); glBindVertexArray(vao); glUseProgram(myprogram); glDrawElements(GL_TRIANGLES, indexCount, GL_UNSIGNED_SHORT, (void *)indexStart); SwapBuffers(GetDC(window_handle));  
    • By Tchom
      Hey devs!
       
      I've been working on a OpenGL ES 2.0 android engine and I have begun implementing some simple (point) lighting. I had something fairly simple working, so I tried to get fancy and added color-tinting light. And it works great... with only one or two lights. Any more than that, the application drops about 15 frames per light added (my ideal is at least 4 or 5). I know implementing lighting is expensive, I just didn't think it was that expensive. I'm fairly new to the world of OpenGL and GLSL, so there is a good chance I've written some crappy shader code. If anyone had any feedback or tips on how I can optimize this code, please let me know.
       
      Vertex Shader
      uniform mat4 u_MVPMatrix; uniform mat4 u_MVMatrix; attribute vec4 a_Position; attribute vec3 a_Normal; attribute vec2 a_TexCoordinate; varying vec3 v_Position; varying vec3 v_Normal; varying vec2 v_TexCoordinate; void main() { v_Position = vec3(u_MVMatrix * a_Position); v_TexCoordinate = a_TexCoordinate; v_Normal = vec3(u_MVMatrix * vec4(a_Normal, 0.0)); gl_Position = u_MVPMatrix * a_Position; } Fragment Shader
      precision mediump float; uniform vec4 u_LightPos["+numLights+"]; uniform vec4 u_LightColours["+numLights+"]; uniform float u_LightPower["+numLights+"]; uniform sampler2D u_Texture; varying vec3 v_Position; varying vec3 v_Normal; varying vec2 v_TexCoordinate; void main() { gl_FragColor = (texture2D(u_Texture, v_TexCoordinate)); float diffuse = 0.0; vec4 colourSum = vec4(1.0); for (int i = 0; i < "+numLights+"; i++) { vec3 toPointLight = vec3(u_LightPos[i]); float distance = length(toPointLight - v_Position); vec3 lightVector = normalize(toPointLight - v_Position); float diffuseDiff = 0.0; // The diffuse difference contributed from current light diffuseDiff = max(dot(v_Normal, lightVector), 0.0); diffuseDiff = diffuseDiff * (1.0 / (1.0 + ((1.0-u_LightPower[i])* distance * distance))); //Determine attenuatio diffuse += diffuseDiff; gl_FragColor.rgb *= vec3(1.0) / ((vec3(1.0) + ((vec3(1.0) - vec3(u_LightColours[i]))*diffuseDiff))); //The expensive part } diffuse += 0.1; //Add ambient light gl_FragColor.rgb *= diffuse; } Am I making any rookie mistakes? Or am I just being unrealistic about what I can do? Thanks in advance
    • By yahiko00
      Hi,
      Not sure to post at the right place, if not, please forgive me...
      For a game project I am working on, I would like to implement a 2D starfield as a background.
      I do not want to deal with static tiles, since I plan to slowly animate the starfield. So, I am trying to figure out how to generate a random starfield for the entire map.
      I feel that using a uniform distribution for the stars will not do the trick. Instead I would like something similar to the screenshot below, taken from the game Star Wars: Empire At War (all credits to Lucasfilm, Disney, and so on...).

      Is there someone who could have an idea of a distribution which could result in such a starfield?
      Any insight would be appreciated
    • By afraidofdark
      I have just noticed that, in quake 3 and half - life, dynamic models are effected from light map. For example in dark areas, gun that player holds seems darker. How did they achieve this effect ? I can use image based lighting techniques however (Like placing an environment probe and using it for reflections and ambient lighting), this tech wasn't used in games back then, so there must be a simpler method to do this.
      Here is a link that shows how modern engines does it. Indirect Lighting Cache It would be nice if you know a paper that explains this technique. Can I apply this to quake 3' s light map generator and bsp format ?
  • Popular Now