PDA

View Full Version : best way to determine vertex occlusion?



bozoface
09-14-2005, 04:45 PM
Hi,

I'd like to determine the visibility of each of about 1000 vertices
that are part of a mesh rendered in the scene. Performance
is not the highest concern, and I'd like the result to work
on both ATI/Nvidia if possible.

So far I've considered the following approaches:

1)
- gluProject each vertex,
- read it's Z from the depth buffer,
- use gluUnProject to get the world space Z (* is this right?)
- compare to the original Z of that vertex.

I implemented this approach, and find it does not work all that well:
the unprojected Z is surprisingly far from the original.
I guess that is due to the quantization down to a single sample
in the Z buffer... but basically I think it is not accurate enough
to judge occlusion, or else (more likely!) there is something
wrong with what I'm doing.

2) Use selection.
- For each point do the selection thing: set a viewport around the
point, render, look at the Z's of objects that show up.

I fear this will be slow and wonder if it will have the issues of approach #1,
i.e., that the point will not necessarily be the closest hit, and
the depths will be too inaccurate to make a simple judgement?

3) Simple approach:
- render the mesh in e.g. Blue
- set depth test to LEQUAL
- render the points in Green (also project them and record their screen x,y)
- read the image back
- look at the color of each of the points.

This will not work because even with LEQUAL, points are often occluded.

4) Put a small bounding box around each point and use one of the
Occlusion extensions.

Would this be expected to work? Drawback is that it would not be widely
supported yet, and I'd still need a fallback approach in case the
card does not support it.

----------------

So, experts! What's the best solution here? Is there any variation
of #3 that could work?

bozoface
09-14-2005, 07:02 PM
I should maybe clarify one thing,

r.e. approach #3, I tried setting the depth test to be LEQUAL
and then draw the vertices (as glPoints) on top of the mesh.
Despite the LEQUAL points "flicker" (become occluded by
the mesh and then unoccluded) as the view changes.
Numerical inaccuracy I presume.