• Advertisement
Sign in to follow this  

OpenGL Questions about deferred shading

This topic is 2603 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi!

I have read that deferred shading is quite simple rendering technique. Although I have tried to get it work for a week already. My demo program is written in OpenGL.

I know how to use Frame Buffers, Multiple Render Targets, Shaders and I know some theory behind deferred shading (have read many articles, slides, googled a lot, downloaded samples).

Questions about G-Buffers.
1) Do I need to render depth or position to the one of the texture? Is there any difference?
2) Is it correct to render depth/positions and normals in camera space or in world space? At the moment position and normal colors are moving with camera.

My english isn't very good, sorry for that :)

Any help will be appreciated!
Karmux

Share this post


Link to post
Share on other sites
Advertisement
Hello,

1.) You can render depth, positions or both. Although currently it is common to render depth only (it saves space, fillrate, etc... e.g. it is faster at same quality).

If you render positions, you have to use 32-bits on all three axis, e.g. GL_RGB32F texture at least.
If you render depth only, you have to use just 32-bits on depth (or even just 24-bits) with GL_R32F (it is most common today), and also I think (not sure) that in GL 3 and higher you can store and use directly depth buffer from frame buffer (it can be either 24 or 32 bits), which will save you one GL_R32F texture in memory and some more fillrate.

Although you have to reconstruct positions from depth of course if you store depth only. Which is fairly simple, but on the other hand imagine an example ... you've got lots and lots of fillrate but not enough computational power - one can store positions then and even have faster application in final ... so of course using depth or positions depends! Although in most cases depth-approach beats positions in performance.

2.) You can work in any space you wish (as long as you have everything in correct = same space), although it is most common to use view (or one can call it camera) space.

Share this post


Link to post
Share on other sites
I personally prefer using the depth rather than a position map. There are issues with the accuracy for some things, but that can be worked around. Plus you get the depth map for free anyway.

Your main issue is that a position map will kill your bandwidth. Even on PC you will be severely bottle necking yourself at higher resolutions. Also there's no way you could fit a position map on the 360 without pain.

I personally do everything in world space, even if it does require the odd matrix inversion and such. I just find it easier to visualise the problem.

Share this post


Link to post
Share on other sites
Thanks for your informative replies! Some things are much clearer.

Now I'm trying to write gbuffer shaders according to your posts.

How do I get vertex position, depth and normal vector in world space in GLSL?

Share this post


Link to post
Share on other sites
Surely you're doing that anyway in your normal lighting calculations???

Transform the vertex into world space then pass through its position to the pixel shader and there you have it. Depth is the distance between camera position and pixel position obviously :)

Share this post


Link to post
Share on other sites
Quote:
Original post by Darg
Transform the vertex into world space then pass through its position to the pixel shader and there you have it.

Following screen (not mine) is correct?
http://home.comcast.net/~agentsnoop/correctwpos.png

-------- My rendering cycle:

1) Clear scene
2) Bind FBO with MRT
3) Bind shader
4)
glGetFloatv(GL_MODELVIEW_MATRIX, mvm);
glGetFloatv(GL_PROJECTION_MATRIX, pm);
gbuffer_shader->set("mvm", mvm);
gbuffer_shader->set("pm", pm);
5) Move camera
6) Draw scene
7) Unbind shader
8) Render FBO to the fullscreen quad

-------- Vertex shader:

varying vec3 vertex_position;
varying vec3 normal_vector;
uniform mat4 mvm;
uniform mat4 pm;
void main() {
gl_Position = mvm * pm * gl_Vertex;
vertex_position = normalize(vec3(mvm * gl_Vertex));
normal_vector = normalize(vec3(gl_NormalMatrix * gl_Normal));
gl_TexCoord[0] = gl_TextureMatrix[0] * gl_MultiTexCoord0;
gl_TexCoord[1] = gl_TextureMatrix[1] * gl_MultiTexCoord1;
}

I don't see nothing on screen. What I'm doing wrong? :(

[Edited by - Karmux on December 10, 2010 1:41:27 PM]

Share this post


Link to post
Share on other sites
Quote:
Original post by Karmux
Quote:
Original post by Darg
Transform the vertex into world space then pass through its position to the pixel shader and there you have it.

Following screen (not mine) is correct?
http://home.comcast.net/~agentsnoop/correctwpos.png

-------- My rendering cycle:

1) Clear scene
2) Bind FBO with MRT
3) Bind shader
4)
glGetFloatv(GL_MODELVIEW_MATRIX, mvm);
glGetFloatv(GL_PROJECTION_MATRIX, pm);
gbuffer_shader->set("mvm", mvm);
gbuffer_shader->set("pm", pm);
5) Move camera
6) Draw scene
7) Unbind shader
8) Render FBO to the fullscreen quad

-------- Vertex shader:

varying vec3 vertex_position;
varying vec3 normal_vector;
uniform mat4 mvm;
uniform mat4 pm;
void main() {
gl_Position = mvm * pm * gl_Vertex;
vertex_position = normalize(vec3(mvm * gl_Vertex));
normal_vector = normalize(vec3(gl_NormalMatrix * gl_Normal));
gl_TexCoord[0] = gl_TextureMatrix[0] * gl_MultiTexCoord0;
gl_TexCoord[1] = gl_TextureMatrix[1] * gl_MultiTexCoord1;
}

I don't see nothing on screen. What I'm doing wrong? :(


Fragment shader?

Share this post


Link to post
Share on other sites
I had a little progress. Now I see scene but all shapes are in position (0,0,0). Translations and rotations in draw_scene() doesn't give any effect.

What I have done so far:
* put 5) before 4) in pipeline
* changed 3rd variable in glUniformMatrix4fv to false
* updated shaders

-------- Vertex Shader:
varying vec3 vertex_position;
varying vec3 normal_vector;
uniform mat4 mm;
uniform mat4 pm;
void main() {
gl_Position = pm * mm * gl_Vertex;
vertex_position = vec3(mm * gl_Vertex);
normal_vector = vec3(gl_NormalMatrix * gl_Normal);
gl_TexCoord[0] = gl_TextureMatrix[0] * gl_MultiTexCoord0;
gl_TexCoord[1] = gl_TextureMatrix[1] * gl_MultiTexCoord1;
}

-------- Fragment Shader:
varying vec3 vertex_position;
varying vec3 normal_vector;
uniform sampler2D texture0, texture1;
vec4 texel, texel0, texel1;
void main() {
texel0 = texture2D(texture0, gl_TexCoord[0].st);
texel1 = texture2D(texture1, gl_TexCoord[1].st);
texel = texel0 * texel1;
gl_FragData[0] = texel;
gl_FragData[1] = vec4(vertex_position, 1);
gl_FragData[2] = vec4(normal_vector, 1);
}


Screen to illustrate things:
http://www.upload.ee/image/977435/positions2.png
This one rectangle should be a box made of 6 rotated rectangles.
There is something wrong with projection matrix.

[Edited by - Karmux on December 11, 2010 5:25:32 AM]

Share this post


Link to post
Share on other sites
You don't seem to ever be taking the world matrix of the individual objects into account.

The correct steps to render a model are as follow:

1: Obtain the objects world matrix from its position, rotation and scale.
2: Pass this world matrix to the vertex shader each time you draw an object.
3: Multiply the incoming vertex position by the world matrix. This gives you the world position of the vertex which is what you want to output to the GBuffer either as position in three 32-bit channels or as depth in one 32-bit channel, I would recommend depth.
4: Multiply this world position by the View and Projection matrices to obtain the view space position of the vertex, this is what is passed through to the pixel shader.

You appear to be completely ignoring the individual objects world matrices.

Share this post


Link to post
Share on other sites
I decided to do deferred rendering in view space.
Depth texture looks fine but when I reconstruct positions then entire screen is green-yellow-red-black.
If I multiply positions by color texture then only my model is green-yellow-red-black and empty space is black and colors are moving with camera.

// Vertex

gl_Position = gl_ModelViewProjectionMatrix * gl_Vertex;
unpro = gl_ModelViewMatrix * gl_Vertex;

// Fragment

float linearize_depth(float z) {
float n = 0.001;
float f = 10.0;
return (2.0 * n) / (f + n - z * (f - n));
}
...
vec3 color = texture2D(color_buffer, gl_TexCoord[0].xy).rgb;
float depth = linearize_depth(texture2D(depth_buffer, gl_TexCoord[0].xy).r);
vec3 normal = texture2D(normal_buffer, gl_TexCoord[0].xy).rgb;
vec4 position = unpro * vec4(gl_FragCoord.xy, depth, 1.0);
position /= position.w;
...
gl_FragColor = position;


Any suggestions are welcome :)

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
    • By Andrey OGL_D3D
      Hi all!
      I try to use the Sun shafts effects via post process in my 3DEngine, but i have some artefacts on final image(Please see attached images).
      The effect contains the following passes:
      1) Depth scene pass;
      2) "Shafts pass" Using DepthPass Texture + RGBA BackBuffer texture.
      3) Shafts pass texture +  RGBA BackBuffer texture.
      Shafts shader for 2 pass:
      // uniform sampler2D FullSampler; // RGBA Back Buffer uniform sampler2D DepthSampler; varying vec2 tex; #ifndef saturate float saturate(float val) {     return clamp(val, 0.0, 1.0); } #endif void main(void) {     vec2 uv = tex;     float sceneDepth = texture2D(DepthSampler, uv.xy).r;     vec4  scene        = texture2D(FullSampler, tex);     float fShaftsMask     = (1.0 - sceneDepth);     gl_FragColor = vec4( scene.xyz * saturate(sceneDepth), fShaftsMask ); } final shader:
      // uniform sampler2D FullSampler; // RGBA Back Buffer uniform sampler2D BlurSampler; // shafts sampler varying vec4 Sun_pos; const vec4    ShaftParams = vec4(0.1,2.0,0.1,2.0); varying vec2 Tex_UV; #ifndef saturate  float saturate(float val) {     return clamp(val, 0.0, 1.0); } #endif vec4 blendSoftLight(vec4 a, vec4 b) {   vec4 c = 2.0 * a * b + a * a * (1.0 - 2.0 * b);   vec4 d = sqrt(a) * (2.0 * b - 1.0) + 2.0 * a * (1.0 - b);       // TODO: To look in Crysis what it the shit???   //return ( b < 0.5 )? c : d;   return any(lessThan(b, vec4(0.5,0.5,0.5,0.5)))? c : d; } void main(void) {     vec4 sun_pos = Sun_pos;     vec2    sunPosProj = sun_pos.xy;     //float    sign = sun_pos.w;     float    sign = 1.0;     vec2    sunVec = sunPosProj.xy - (Tex_UV.xy - vec2(0.5, 0.5));     float    sunDist = saturate(sign) * saturate( 1.0 - saturate(length(sunVec) * ShaftParams.y ));     sunVec *= ShaftParams.x * sign;     vec4 accum;     vec2 tc = Tex_UV.xy;     tc += sunVec;     accum = texture2D(BlurSampler, tc);     tc += sunVec;     accum += texture2D(BlurSampler, tc) * 0.875;     tc += sunVec;     accum += texture2D(BlurSampler, tc) * 0.75;     tc += sunVec;     accum += texture2D(BlurSampler, tc) * 0.625;     tc += sunVec;     accum += texture2D(BlurSampler, tc) * 0.5;     tc += sunVec;     accum += texture2D(BlurSampler, tc) * 0.375;     tc += sunVec;     accum += texture2D(BlurSampler, tc) * 0.25;     tc += sunVec;     accum += texture2D(BlurSampler, tc) * 0.125;     accum  *= 0.25 * vec4(sunDist, sunDist, sunDist, 1.0);           accum.w += 1.0 - saturate(saturate(sign * 0.1 + 0.9));     vec4    cScreen = texture2D(FullSampler, Tex_UV.xy);           vec4    cSunShafts = accum;     float fShaftsMask = saturate(1.00001 - cSunShafts.w) * ShaftParams.z * 2.0;              float fBlend = cSunShafts.w;     vec4 sunColor = vec4(0.9, 0.8, 0.6, 1.0);     accum =  cScreen + cSunShafts.xyzz * ShaftParams.w * sunColor * (1.0 - cScreen);     accum = blendSoftLight(accum, sunColor * fShaftsMask * 0.5 + 0.5);     gl_FragColor = accum; } Demo project:
      Demo Project
      Shaders for postprocess Shaders/SunShaft/
      What i do wrong ?
      Thanks!
       


  • Advertisement