Sign in to follow this  
mdwh

OpenGL Clip planes on NVIDIA with Shaders?

Recommended Posts

mdwh    1108
My NVIDIA 8600GT supports user clip planes, but only when using the fixed pipeline. Is there any way to enable them when using shaders? I've occasionally come across places suggesting this is possible (e.g., a comment here suggests it works if you "write a clip distance to result.clip[0] in your vertex program"), but I don't know enough to know how to implement that? I'm using Cg and OpenGL if that makes any difference. Note, I've tried Oblique Depth Projection, but it doesn't work for me - please see this thread for details on that. Thanks in advance.

Share this post


Link to post
Share on other sites
TheAdmiral    1122
IIRC, clip planes are implemented as a texkill in the FFP's pixel shader anyway, so there's nothing to gain from enabling this mechanism. Is there a reason you can't test the world-space coordinate against the appropriate plane equation like everyone else? It's a two-liner.

Share this post


Link to post
Share on other sites
jamesw    400
From what I've heard on Geforce 6&7 clip planes are implemented with texkill, so as to not change the results of rasterization due to floating point imprecision. It's much more efficient than doing it yourself though, because triangles completely on one side of the plane are not rasterized at all, and only triangles intersecting the clip plane use texkill. Geforce 8 however actually splits triangles and so you can get some nasty z-fighting with multipass techniques if you enable clip planes in later passes, so you have to use a depth bias. I get the z-fighting from ATI cards too so I can only assume they also do the geometry approach.

Share this post


Link to post
Share on other sites
Trenki    345
User clip planes together with shaders have some issues. In GLSL you would have to write to gl_ClipVertex. On some hardware that might not be enough, but I don't know if it's Nvidia or ATI hardware.

AFAIK on GF6/7 the user clip planes are implemented using texkill, but for GF8 and other DX10 hardware this is probably not an option since the geometry shader has to be feed with fully clipped geometry.

Share this post


Link to post
Share on other sites
for many cases doing the clipping in the pixel shader is the easiest way. There are few gains from a user clip plane on current hardware in my experience...

To do clipping in a shader is easy:

the clip(x) function in HLSL for example clips out pixels if any component of x<0

so basically in your vertex shader just find where a vertex should be clipped using whatever method you want..(it's easy for rectilinear planes, a bit harder for other rotations).

Like say i want to clip all pixels below the coord (0,0,0) ..i define a variable x=worldpos.y and pass this to the pixel shader where all you do is call clip(x) .. and everything negative will be clipped out...

Share this post


Link to post
Share on other sites
mdwh    1108
Thanks, doing clipping in the shaders with clip() seems to work fine!

OTOH, I came across this thread where people were suggesting this could give poor performance, I don't know what the current view on this is?

Still, it seems to work well enough, so I'm happy.

One thing, my scene currently mixes shaders with fixed pipeline (I haven't got round to writing shaders for everything, though I guess I could), and so I'm setting the OpenGL user clip plane as well, I don't know if this will cause problems on some cards (I mean, I would hope they either are implemented properly, or ignored).

Share this post


Link to post
Share on other sites
LeGreg    754
Quote:
Original post by mdwh
Thanks, doing clipping in the shaders with clip() seems to work fine!

OTOH, I came across this thread where people were suggesting this could give poor performance, I don't know what the current view on this is?


It would give you less than optimal performance compared to fixed clip planes, for multiple reasons. The shader has to be executed for all pixels even those that are clipped, the early z acception/rejection can also be disabled on some hardware if you kill pixels in the shader (and early z is one of the nice thing of modern 3d hardware).

Of course if you're less concerned by performance, more with flexibility (you can have a larger number of clip planes with clip()) and/or with depth invariance (to avoid z-fighting) then clip is a good solution (you can also fight z-fighting with a depth bias of course).

LeGreg

Share this post


Link to post
Share on other sites
Jerax    126
GF 6 and 7 have 6 hardware clip planes (as in real clip planes that clip before the fragment shader, not texkill). I've had some very significant speed improvements by using them to reduce fragment shader load. However, I've only ever used them from D3D, so I'm not sure how you'd enable them in OGL (if it's even possible).

In fact according to a quick search in the driver caps database, nvidia cards ahve had clip planes since GF FX series cards, and ATI since Radeon 7500.

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