Although I am not a paraview user could you point to some data files and a quick howto that would allow us to really stress paraview? To be honest running lots of applications out of the box, without knowing the software always makes for lot's of challenges... Regards, Matt -------------------------- Sent from my BlackBerry Wireless Handheld -----Original Message----- From: Mathieu Malaterre <mmalater at nycap dot rr dot com> To: Donovan Baarda <abo at minkirri dot apana dot org dot au> CC: flavio-fglrx at stanchina dot net <flavio-fglrx at stanchina dot net> Sent: Sat Apr 09 20:49:04 2005 Subject: Re: [fglrx] VTK + fglrx Donovan Baarda wrote:
On Fri, 2005-04-08 at 20:32 -0400, Mathieu Malaterre wrote:Just for history, here are the ways I found to use VTK and fglrx. 1. Comment the line "Load dri" or turn the no_dri to true: [fglrx config] Option "no_dri" "yes" 2. Using clone mode apparently remove driDoesn't turning off DRI turn off 3D acceleration?3. export LIBGL_ALWAYS_INDIRECT=1 before starting the app.And from what I've read, indirect mode also turns off 3D acceleration. There has been some discussion on the XOrg lists about indirect 3D acceleration, but it isn't implemented yet.
Well my whole point was to get VTK/ParaView to work on ATI. Unless you trick the compilation to use Mesa and play with LD_PRELOAD, the solutions I proposed were only to help simple user that want both VTK and 3D acceleration in, let say, glxgears... Mathieu