[vtkusers] Bug in depth ordering whilst rendering

[Jeff Lee]

If these artifact are independent of whether you have opacity set or not, it
is probably a depth-buffering issue.  What happens when you setenv
GL_DEPTH_BITS 32 and relaunch your app?
-J

On 11/28/07, Peter Clifton <pcjc2 at cam.ac.uk> wrote:
>
>
> On Wed, 2007-11-28 at 00:49 -0800, David Thompson wrote
> > >> The rendering
> > >> "SetOpacity(0.999)" calls to some other value, e.g. 1.5 would stop
> > >> the
> > >> bug manifesting.
> > Any value above 1.0 gets clamped to 1.0 (fully opaque) and would thus
> > not present a problem.
>
> What algorithm / section of code is used when rendering opaque objects
> to ensure those nearest the camera occlude those further away?
>
> I'll post a sane example later today. Is python code running in Mayavi
> Python acceptable for examples, or should I try to distill it down to
> purer Python + VTK?
>
> --
> Peter Clifton
>
> Electrical Engineering Division,
> Engineering Department,
> University of Cambridge,
> 9, JJ Thomson Avenue,
> Cambridge
> CB3 0FA
>
> Tel: +44 (0)7729 980173 - (No signal in the lab!)
>
> _______________________________________________
> This is the private VTK discussion list.
> Please keep messages on-topic. Check the FAQ at:
> http://www.vtk.org/Wiki/VTK_FAQ
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtkusers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20071128/7ff39b93/attachment.htm>