[vtkusers] Re: Mesa/VTK problem on RedHat 7.2 (also with Mesa 4.0) [CORRECTION]

[Dave Reed]

> From: Prabhu Ramachandran <prabhu at aero.iitm.ernet.in>
> Content-Type: text/plain; charset=us-ascii
> Date: Sun, 18 Nov 2001 23:33:34 +0530
> Cc: vtkusers at public.kitware.com, mesa3d-users at lists.sourceforge.net
> Reply-To: Prabhu Ramachandran <prabhu at cyberwaveindia.com>
> Sender: Prabhu Ramachandran <prabhu at squid.cyberwaveindia.com>
> Content-Length: 979
> 
> >>>>> "DR" == Dave Reed <dreed at capital.edu> writes:
> 
>     >> Note that I have not tried this myself but if Ann's patch is
>     >> correct I guess this should be correct too.  According to Hank
>     >> Childs <childs at hyper.llnl.gov> this problem occurs because of a
>     >> problem in display lists.  Maybe you could confirm this
>     >> behaviour by trying this change and checking if you still have
>     >> missing polygons.  This might help the mesa folks.
> 
>     DR> Yes, making that change to the VTK code fixes the problem. So
>     DR> the problem is with Mesa display lists and triangle strips?
> 
> Great!  One way to do this without a rebuild is to call
> ImmediateModeRenderingOn() on all the mappers.  This should turn off
> display lists.


Sorry, I messed up. I forgot to put the triangle stripper back
in. When I did that, it still didn't work even with the change to
vtkOpenGLPolyDataMapper. With either version of the
vtkOpenGLPolyDataMapper code, it doesn't work with the triangle
stripper. Taking the triangle stripper out makes it work for either
one.

That seems to indicate the problem is in Mesa's triangle strip
rendering, not the display lists.


> Yes, according to Hank Childs the problem is with display lists.  the
> else block after the if condition is called if the mapper is using
> display lists.  If the Mesa folks want to see the OpenGLPolyDataMapper
> code please do let us know.

Dave