[vtkusers] Re: RedHat 7.2 Mesa bug with VTK?

[Dave Reed]

> From: Prabhu Ramachandran <prabhu at aero.iitm.ernet.in>
> Content-Type: text/plain; charset=us-ascii
> Reply-To: Prabhu Ramachandran <prabhu at cyberwaveindia.com>
> Sender: vtkusers-admin at public.kitware.com
> X-BeenThere: vtkusers at public.kitware.com
> X-Mailman-Version: 2.0.6
> Precedence: bulk
> List-Help: <mailto:vtkusers-request at public.kitware.com?subject=help>
> List-Post: <mailto:vtkusers at public.kitware.com>
> List-Subscribe: <http://public.kitware.com/mailman/listinfo/vtkusers>,
> 	<mailto:vtkusers-request at public.kitware.com?subject=subscribe>
> List-Id: <vtkusers.public.kitware.com>
> List-Unsubscribe: <http://public.kitware.com/mailman/listinfo/vtkusers>,
> 	<mailto:vtkusers-request at public.kitware.com?subject=unsubscribe>
> List-Archive: <http://public.kitware.com/pipermail/vtkusers/>
> Date: Thu, 25 Oct 2001 13:36:21 +0530
> Content-Length: 1268
> 
> hi,
> 
> >>>>> "DR" == Dave Reed <dreed at capital.edu> writes:
> 
>     DR> Anyone else running VTK on RedHat 7.2 yet (using Mesa)?
> 
>     DR> When I run the medical1.cxx example, the skin has two "holes"
>     DR> in it (missing polygons). The problem happens both on a laptop
>     DR> with a Rage Mobility chipset and with a TNT2 card. I tried the
>     DR> NVidia drivers on the TNT2 machine and the problem goes
>     DR> away. I asked on the Mesa list and Brian Paul said:
> 
> I guess this means you are using the 3.2 release.  Maybe its fixed in
> the 4.0 release?  I will try and get back to you.

Note that it did work ok under RedHat 7.1 (can't remember what version
of Mesa that came with).

Yes, I'm using a vtk nightly release from back in July. Please do let
me know if 4.0 solves it.



> <snip>
> 
>     DR> But that didn't produce any errors so I'm wondering if it's
>     DR> something else. Anyone else verify the problem or provide any
>     DR> insights?
> 
> Well, this wont help but its worth knowing that there is another
> problem with display lists when using VTK and Mesa on Linux( or maybe
> all *nix?) systems.  Here too the problem is Mesa specific.  It has
> been reported here:
> 
> http://public.kitware.com/pipermail/vtkusers/2001-September/007664.html
> 
> I havent yet reported it to the Mesa lists (could you help with
> this?).


Mesa 3.1 is pretty old so I'm sure the first suggestion would be to
update Mesa. I'd rather wait until you have a newer Mesa before
reporting it to the Mesa list if you don't mind.

Dave