vtkKWEGPUInfoList is mandatory. What's not mandatory is the installation of the DirectX SDK on Windows (that's a big beast) or NVCtrl library on Linux (installation is easy but not trivial).
If those third-party libraries are not set, a vtkKWEDummyGPUInfoList is used and returns 0MB of VRAM. But in this case, the GPU volume mapper takes a user-defined ivar "MaxMemoryInBytes" into account (if this value is 0, which means not set, the GPU mapper assumes 128MB of VRAM) I just updated the VTKEdge FAQ ( http://vtkedge.org/Wiki/VTKEdge:FAQ ) with two questions: * How can I make vtkKWEGPUVolumeRayCastMapper run as fast as in VolView 3.0? * What is the difference between vtkKWEGPUVolumeRayCastMapper and vtkKWEVolumeRayCastMapper? I also added the following item in the compile time section: "you don't need any special setting to use the vtkKWEGPUInfo class under Mac OS X. " BTW, my name is Francois... Francoise is the female equivalent :-) Regards. On Fri, May 8, 2009 at 11:11 AM, Michael Knopke <[email protected]> wrote: > Francoise! You’re the man! Now VR totally rocks! > > > > It seems to me that gpuinfo should be made mandatory, otherwise it’s kind of > irritating for users having build the vrendering demo, but getting the > results from vtkTextureMapper3D. > > > > Regards, > > > > Michael > > _______________________________________________ > VtkEdge mailing list > [email protected] > http://public.kitware.com/cgi-bin/mailman/listinfo/vtkedge > > -- François Bertel, PhD | Kitware Inc. Suite 204 1 (518) 371 3971 x113 | 28 Corporate Drive | Clifton Park NY 12065, USA _______________________________________________ VtkEdge mailing list [email protected] http://public.kitware.com/cgi-bin/mailman/listinfo/vtkedge
