[vtkusers] VTK 5.6.0 vtkGPUVolumeRayCastMapper very slow?

[Elvis Chen]

Again, thank you for the reply.  I've installed the DirectX SDK and
recompiled VTK.  The demo now runs well (though I have no TestGPUInfo in my
build).

As a side question, is there any plan to integrate CUDA based volume
rendering technique into VTK (e.g.
http://www.slicer.org/slicerWiki/index.php/Slicer3:Volume_Rendering_With_Cuda)?
 I've got Benjamin's code to work before, but his code is far from polished.

On Tue, May 11, 2010 at 2:26 PM, Francois Bertel <
francois.bertel at kitware.com> wrote:

> Yes you can use the latest DirectX SDK (side note: there are two
> DirectX SDK releases per year, one in February, one in August).
>
> I currently use the Feb 2010 one.
>
> Once your done building VTK, run the test TestGPUInfo in verbose mode
> to see if the returned information makes sense:
>
> For example, on Vista 64 SP1 with a nVidia Quadro FX 3600M, 512MB, I have:
>
> > cd vtk-build
> > ctest.exe -R TestGPUInfo -V
> ...
> 160: Test command: C:\vtk-build\bin\Debug\RenderingCxxTests.exe
> TestGPUInfo -D C:/VTKData -T C:/vtk-build/Testing/Temporary -V
> Baseline/Rendering/TestGPUInfo.png
> 160: Test timeout computed to be: 1500
> 160: There is 1 GPU(s).
> 160:  GPU 0:
> 160:   dedicated VRAM=495 MB
> 160:   dedicated RAM=0 MB
> 160:   shared RAM=1791 MB
> 1/1 Test #160: TestGPUInfo ......................   Passed    0.13 sec
> ...
>
> You can see that 495MB is less than 512MB. This is probably the
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20100512/1a7fb7ed/attachment.htm>