• 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
Squidshire

OpenGL
Geometry shaders and depth FBOs

4 posts in this topic

Hi

Are there any special rules regarding rendering to an FBO when there's a geometry shader involved?

Context:
I'm trying to implement shadow mapping in a scene which includes different types of objects being rendered in different ways:
Meshes, rendered in the standard way through VBOs and shaders
Point sprite particles, rendered with a vertex and fragment shader
Quad particles, sent in as points but expanded to quads in a geometry shader

I'm doing shadow mapping in the standard way, which involves creating a depth FBO and rendering to it the object's depths from the light's point of view. The meshes and point sprites work fine, but the depths of the geometry shader quad particles aren't being rendered to the FBO.

[url="http://i.imgur.com/hxpVE.png"]Here[/url]'s the standard (non-FBO) depth buffer. Note the large circular-shaped particles in the foreground.

[url="http://i.imgur.com/IJlXp.png"]Here[/url]'s the same view rendered to the FBO. Note that only the depths of the meshes and point sprite particles are drawn.

My FBO is set up as follows (it's based on Chapter 7 from the [i]OpenGL 4 Shading Language Cookbook[/i]):
[CODE]const bool Renderer::generateShadowMap(FBO & f, string & error) {
uint depthTexID;
uint width = f.getWidth();
uint height = f.getHeight();
glGenTextures(1, &depthTexID);
glBindTexture(GL_TEXTURE_2D, depthTexID);
glTexImage2D( GL_TEXTURE_2D, 0, GL_DEPTH_COMPONENT,
width, height, 0,
GL_DEPTH_COMPONENT, GL_FLOAT, NULL);
float border[] = {1.0, 0.0, 0.0, 0.0};
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_BORDER);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_BORDER);
glTexParameterfv(GL_TEXTURE_2D, GL_TEXTURE_BORDER_COLOR, border);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_COMPARE_MODE, GL_COMPARE_REF_TO_TEXTURE);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_COMPARE_FUNC, GL_LESS);
glActiveTexture(GL_TEXTURE1);
glBindTexture(GL_TEXTURE_2D, depthTexID);
uint fID;
glGenFramebuffers(1, &fID);
glBindFramebuffer(GL_FRAMEBUFFER, fID);
glFramebufferTexture2D(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, GL_TEXTURE_2D, depthTexID, 0);
glDrawBuffer(GL_NONE);
if(!checkFBOstatus(error)) {
cerr << error << endl;
return false;
}
glClearDepth(1.0);
glClear(GL_DEPTH_BUFFER_BIT);
glBindFramebuffer(GL_FRAMEBUFFER, 0);
glActiveTexture(GL_TEXTURE0);
f.setFBOID(fID);
f.setTexID(depthTexID);
return true;
}[/CODE]

The shaders that should render the depths of the quad particles are:
[CODE]
//VERTEX SHADER
#version 400
in vec3 aPosition;
in float aSize;
out float gSize;
uniform mat4 vWorldView;
void main() {
gSize = aSize;
vec4 v4Vertex = vec4(aPosition.xyz, 1.0);
vec4 transformedVertex = vWorldView * v4Vertex;
gl_Position = transformedVertex;
}
//GEOMETRY SHADER
#version 400
layout (points) in;
layout (triangle_strip, max_vertices = 4) out;
in float gSize[1];
uniform mat4 vgProjection;
void main() {
vec4 oPosition;

float halfSize = gSize[0] * 0.5;
oPosition = (vec4(-halfSize, -halfSize, 0.0, 0.0) + gl_in[0].gl_Position);
gl_Position = vgProjection * oPosition;
EmitVertex();

oPosition = (vec4(halfSize, -halfSize, 0.0, 0.0) + gl_in[0].gl_Position);
gl_Position = vgProjection * oPosition;
EmitVertex();

oPosition = (vec4(-halfSize, halfSize, 0.0, 0.0) + gl_in[0].gl_Position);
gl_Position = vgProjection * oPosition;
EmitVertex();

oPosition = (vec4(halfSize, halfSize, 0.0, 0.0) + gl_in[0].gl_Position);
gl_Position = vgProjection * oPosition;
EmitVertex();
EndPrimitive();
}
//FRAGMENT SHADER - empty as depth should be written automatically
#version 400
void main() {
}
[/CODE]
Depth testing is enabled, of course. I've also tried telling the fragment shader to try to draw something to see if that makes a difference.

I've run this through gDebugger which can't detect any errors at all. I've tried telling the fragment shader to actually draw things but that doesn't make a difference either.

The only difference between the point sprite particles and the quad particles is the use of the geometry shader. I'm rendering both at the same time and with the same uniform values (and I've run gDebugger to make sure).

I've tested this on a computer with a nVidia GTX 560 Ti with driver version 8.17.13.142 (the latest, I believe, at the time of writing) and another with a Radeon Mobility HD 5650. I get the same result on both.

Am I making any obvious mistakes or are there some specific things I should know about?

Thanks
1

Share this post


Link to post
Share on other sites
I managed to fix the problem, but I have another issue.

The solution: the shadows weren't being drawn as I had enabled front face culling for the rendering of shadows. Changing the order of the vertices in the geometry shader fixed it.

New issue:
Because the depth of the shadow is essentially the same as the depth of the particle itself, every particle will be affected by its own shadow.

[url="http://i.imgur.com/UPcgl.png"]Image[/url] (ignore the "particle transparency" bit - it's part of the HUD)

I've tried applying a polygon offset through glPolygonOffset (for lines, points and fill) but it only seems to affect the shadows cast by the mesh objects (not built in a geometry shader). I've also tried messing about with the gl_FragDepth (so the particle fragments would be treated as closer to the camera, and the particle shadows would be treated as being further away), but that gave no change other than the particle or its shadow completely disappearing when the depth was outside of the 0 to 1 range.
I also tried changing the screen-space depth of the shadow vertices themselves. Lower offsets removed the self shadow but also displaced the positions of the shadows on other objects.

[url="http://i.imgur.com/YRapE.png"]Image[/url]

I then tried to draw the particles closer to the screen so that their screen-space depths would be lower than that of the shadows. Applying the offset before the projection transformation (but after applying the modelview matrix) displaced the particles according to the camera position but otherwise did not affect the shadows. Applying it after projection seemed to change the distance at which the particle could be seen but didn't change the shadow at all.

What am I doing wrong? Is this issue actually possible to solve?

Thanks
0

Share this post


Link to post
Share on other sites
[quote name='Squidshire' timestamp='1343485434' post='4963967']
the shadows weren't being drawn as I had enabled front face culling for the rendering of shadows. Changing the order of the vertices in the geometry shader fixed it.
[/quote]
Instead of changing the order of the vertices, it is easier to changing the culling with "glCullFace(GL_FRONT)" or "glCullFace(GL_BACK)". Or as you don't want culling at all for 2D objects, you could simply disable it.
[quote]I also tried changing the screen-space depth of the shadow vertices themselves. Lower offsets removed the self shadow but also displaced the positions of the shadows on other objects.[/quote]
This is usually the solution. Use a small epsilon when comparing depths. It is easier than to manipulate where you draw things. In practice, you move the shadow "epsilon" units away. You may need different values for this epsilon depending on the situation. The particles, being 2D, can probably have a small epsilon. Big objects, where you use front face culling, can maybe have 0 as epsilon. The back side of objects shadowing themselves is obviously no problem.
1

Share this post


Link to post
Share on other sites
Thanks for the suggestion. I went back to take another look. The issue seems to be that if I move the shadows back, then they will vanish entirely (the particles won't shadow themselves, but won't shadow anything else either).

[url="http://i.imgur.com/NfHx7.png"]http://i.imgur.com/NfHx7.png[/url] (screenshot - ignore the "particle" text, which is part of the HUD).

I suppose I could use two separate shadow maps - one for particles where the depth is offset slightly, and one for meshes where the depth remains the same.
0

Share this post


Link to post
Share on other sites
[quote name='Squidshire' timestamp='1343666428' post='4964545']
Thanks for the suggestion. I went back to take another look. The issue seems to be that if I move the shadows back, then they will vanish entirely (the particles won't shadow themselves, but won't shadow anything else either).

[url="http://i.imgur.com/NfHx7.png"]http://i.imgur.com/NfHx7.png[/url] (screenshot - ignore the "particle" text, which is part of the HUD).

I suppose I could use two separate shadow maps - one for particles where the depth is offset slightly, and one for meshes where the depth remains the same.
[/quote]

Or you have two different shaders. One for the particles and one for the meshes. Can also be implemented by a conditinal statement in the shader.
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 Toastmastern
      So it's been a while since I took a break from my whole creating a planet in DX11. Last time around I got stuck on fixing a nice LOD.
      A week back or so I got help to find this:
      https://github.com/sp4cerat/Planet-LOD
      In general this is what I'm trying to recreate in DX11, he that made that planet LOD uses OpenGL but that is a minor issue and something I can solve. But I have a question regarding the code
      He gets the position using this row
      vec4d pos = b.var.vec4d["position"]; Which is then used further down when he sends the variable "center" into the drawing function:
      if (pos.len() < 1) pos.norm(); world::draw(vec3d(pos.x, pos.y, pos.z));  
      Inside the draw function this happens:
      draw_recursive(p3[0], p3[1], p3[2], center); Basically the 3 vertices of the triangle and the center of details that he sent as a parameter earlier: vec3d(pos.x, pos.y, pos.z)
      Now onto my real question, he does vec3d edge_center[3] = { (p1 + p2) / 2, (p2 + p3) / 2, (p3 + p1) / 2 }; to get the edge center of each edge, nothing weird there.
      But this is used later on with:
      vec3d d = center + edge_center[i]; edge_test[i] = d.len() > ratio_size; edge_test is then used to evaluate if there should be a triangle drawn or if it should be split up into 3 new triangles instead. Why is it working for him? shouldn't it be like center - edge_center or something like that? Why adding them togheter? I asume here that the center is the center of details for the LOD. the position of the camera if stood on the ground of the planet and not up int he air like it is now.

      Full code can be seen here:
      https://github.com/sp4cerat/Planet-LOD/blob/master/src.simple/Main.cpp
      If anyone would like to take a look and try to help me understand this code I would love this person. I'm running out of ideas on how to solve this in my own head, most likely twisted it one time to many up in my head
      Thanks in advance
      Toastmastern
       
       
    • By fllwr0491
      I googled around but are unable to find source code or details of implementation.
      What keywords should I search for this topic?
      Things I would like to know:
      A. How to ensure that partially covered pixels are rasterized?
         Apparently by expanding each triangle by 1 pixel or so, rasterization problem is almost solved.
         But it will result in an unindexable triangle list without tons of overlaps. Will it incur a large performance penalty?
      B. A-buffer like bitmask needs a read-modiry-write operation.
         How to ensure proper synchronizations in GLSL?
         GLSL seems to only allow int32 atomics on image.
      C. Is there some simple ways to estimate coverage on-the-fly?
         In case I am to draw 2D shapes onto an exisitng target:
         1. A multi-pass whatever-buffer seems overkill.
         2. Multisampling could cost a lot memory though all I need is better coverage.
            Besides, I have to blit twice, if draw target is not multisampled.
       
    • By mapra99
      Hello

      I am working on a recent project and I have been learning how to code in C# using OpenGL libraries for some graphics. I have achieved some quite interesting things using TAO Framework writing in Console Applications, creating a GLUT Window. But my problem now is that I need to incorporate the Graphics in a Windows Form so I can relate the objects that I render with some .NET Controls.

      To deal with this problem, I have seen in some forums that it's better to use OpenTK instead of TAO Framework, so I can use the glControl that OpenTK libraries offer. However, I haven't found complete articles, tutorials or source codes that help using the glControl or that may insert me into de OpenTK functions. Would somebody please share in this forum some links or files where I can find good documentation about this topic? Or may I use another library different of OpenTK?

      Thanks!
    • 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));  
  • Popular Now