Hi, I'm trying to implement graphic pipeline in software level. I have some problems with clipping and culling now.
Basically, there are two main concerns:
We get it. We use ad blockers too. But GameDev.net displays them so we can continue to be a great platform for you.
Please whitelist GameDev.net and our advertisers.
Also consider a GDNet+ Pro subscription to remove all ads from GameDev.net.
Subscribe to GameDev.net's newsletters to receive the latest updates and exclusive content.
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.
Posted 15 February 2013 - 12:44 PM
Hi, I'm trying to implement graphic pipeline in software level. I have some problems with clipping and culling now.
Basically, there are two main concerns:
Posted 15 February 2013 - 02:15 PM
Super quick answer, when I did this I clipped in screen space (2D) after back-face culling (also in screen space using winding).
You reconstruct the triangles with interpolation but you need to multiply/divide by w to account for the perspective correction.
While screen space might not be optimal, it is very easy, plus you only have to transform each vertex only once.
Good luck ;)
Posted 15 February 2013 - 02:45 PM
Super quick answer, when I did this I clipped in screen space (2D) after back-face culling (also in screen space using winding).
You reconstruct the triangles with interpolation but you need to multiply/divide by w to account for the perspective correction.
While screen space might not be optimal, it is very easy, plus you only have to transform each vertex only once.
Good luck ;)
Thanks for the reply. I think I might try that out if there is no better suggestion.
Posted 17 February 2013 - 10:43 AM
When I did the occlusion software rasterizer for Urho3D, I remember encountering some precision/overflow issues when clipping in screen space against the near plane. Basically, the X/Y coordinates could become huge if the near clipping plane was near 0. Therefore I switched to clipping in homogenous coordinates before perspective divide. When you reconstruct triangles in homogenous coords, just interpolate all of x,y,z,w after you find where an edge intersects with the clip plane in question. Note that clipping against all frustum planes can theoretically generate a large amount of new vertices & triangles.
If you want to check, the file in question is OcclusionBuffer.cpp.
Every time you add a boolean member variable, God kills a kitten. Every time you create a Manager class, God kills a kitten. Every time you create a Singleton...
Posted 17 February 2013 - 01:59 PM
When I did the occlusion software rasterizer for Urho3D, I remember encountering some precision/overflow issues when clipping in screen space against the near plane. Basically, the X/Y coordinates could become huge if the near clipping plane was near 0. Therefore I switched to clipping in homogenous coordinates before perspective divide. When you reconstruct triangles in homogenous coords, just interpolate all of x,y,z,w after you find where an edge intersects with the clip plane in question. Note that clipping against all frustum planes can theoretically generate a large amount of new vertices & triangles.
If you want to check, the file in question is OcclusionBuffer.cpp.
Thanks, I just implemented clipping only with near plane which cares only about z value. As for x, y value, my workaround is to clamp the bounding-box in screen space for every triangle passed into rasterizer.
A confusion about reconstructing triangle in homogeneous coordinate. How do you know the clipping in homogeneous coordinate? I mean I have information of view frustum before projection transformation, but after that vertices are transformed into clipping coordinate, should I also do projection transformation on view frustum?
Sorry for my poor English, even myself no sure what I mean.
Posted 18 February 2013 - 03:14 AM
After projection transform, the view volume is fixed (in Direct3D convention, left clip plane at X -1.0, far clip plane at Z 1.0, near clip at Z 0.0) so there should be no need to transform the frustum.
Every time you add a boolean member variable, God kills a kitten. Every time you create a Manager class, God kills a kitten. Every time you create a Singleton...
Posted 18 February 2013 - 03:27 AM
I think I get you. But is it a typo or something? because In your last post you said you did clipping in homogeneous coordinate before perspective divide, namely in clipping coordinate. But clipping coordinate doesn't have fixed view volume which is in NDC(normalized device coordinate).After projection transform, the view volume is fixed (in Direct3D convention, left clip plane at X -1.0, far clip plane at Z 1.0, near clip at Z 0.0) so there should be no need to transform the frustum.
Posted 18 February 2013 - 04:09 AM
Ah, I took a bit of a shortcut. What I should have said that after projection & perspective divide the vertices sit inside the fixed view volume. But the end result is, that when you're clipping homogenous coordinates using 4-dimensional dot products, you can use those fixed clipping planes.
Every time you add a boolean member variable, God kills a kitten. Every time you create a Manager class, God kills a kitten. Every time you create a Singleton...
Posted 23 February 2013 - 03:14 PM
Ah, I took a bit of a shortcut. What I should have said that after projection & perspective divide the vertices sit inside the fixed view volume. But the end result is, that when you're clipping homogenous coordinates using 4-dimensional dot products, you can use those fixed clipping planes.
After all these days, I still can't get clear about the clipping and reconstruction of triangle. Say triangle Tp has been left multiplied by perspective matrix but not yet divided by its fourth component w. Should I now do the clipping and reconstruction? if I do clipping and reconstruction in this stage, what clipping plane should I clip against?
Posted 23 February 2013 - 03:40 PM
You can do it either way - mathematically they both will work, but they just use slightly different operations. If you want to clip after the w-divide, then it is fairly simple to do since the view volume occupies the ranges that AgentC mentioned (x : [-1,1], y : [-1,1], z : [0,1]). If you do it before w-divide, then you have to use a different type of clipping. It is a bit of an involved derivation, but there is a pretty good explanation of it in Dave Eberly's book 3D Game Engine Design, 2nd edition. If you get the book, look in chapter 2.4.
By doing the clipping before the divide, you are also able to do the perspective correct interpolation with the new vertices.
Jason Zink :: DirectX MVP
Direct3D 11 engine on CodePlex: Hieroglyph 3
Direct3D Books: Practical Rendering and Computation with Direct3D 11, Programming Vertex, Geometry, and Pixel Shaders
Articles: Dual-Paraboloid Mapping Article :: Parallax Occlusion Mapping Article (original):: Fast Silhouettes Article
Games: Lunar Rift
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.
GameDev.net™, the GameDev.net logo, and GDNet™ are trademarks of GameDev.net, LLC.