Sign in to follow this  
Ectara

OpenGL W coordinate equals zero during homogenous divide

Recommended Posts

Ectara    3097
I have an issue in my software renderer where if a polygon straddles the near clipping plane, there's a chance that one of the vertices will have a w coordinate of zero after the matrix transformation. I know that in OpenGL, this problem doesn't occur, with the same exact scene. Is there any technique to avoid this issue?

Share this post


Link to post
Share on other sites
haegarr    7372
The problem obviously occurs due to your choice of projection matrix. You haven't told anything about that matrix, but you know that OpenGL's corresponding projection matrix doesn't have this issue, so my suggestion is to analyze OpenGL's matrix (it is publicly available n the internet) and compare its way of doing things with yours.

Share this post


Link to post
Share on other sites
Krypt0n    4721
usually you don't draw until z is zero, but just to the near clipping plane, which is in some distance to 0.

obviously, simplest way to solve that is probably to clip your triangles on the near plane before you divide by w.

Share this post


Link to post
Share on other sites
Ectara    3097
[quote]The problem obviously occurs due to your choice of projection matrix.[/quote]
@haegarr
The problem is not my projection matrix; I've compared them several times while writing the renderer, and researched it. Not to mention, it's nonzero after the projection matrix multiply, but after the modelview matrix multiply, which places the polygon on/near the near plane, the w coordinate becomes zero. The problem obviously lies elsewhere.

perspective(50.0f, 1.33333f, 0.1f, 500.0f), which works fine everywhere else.

[quote]usually you don't draw until z is zero, but just to the near clipping plane, which is in some distance to 0.obviously, simplest way to solve that is probably to clip your triangles on the near plane before you divide by w.[/quote]
@Krypt0n
I will attempt better clipping; I usually transform and keep the vertices unclipped for interpolation reasons, but this is unacceptable.

Share this post


Link to post
Share on other sites
WedgeMan    100
I had this problem as well recently implementing a software renderer. It has nothing to do with your projection matrix specifically, it has to do with all projection matrices in general.

You simply need to implement clipping on your triangles so that they can't go past the near clip plane. You won't get divide by 0 issues then.

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 povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
       
    • 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.
  • Popular Now