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).<div><br></div><div>As a side question, is there any plan to integrate CUDA based volume rendering technique into VTK (e.g. <a href="http://www.slicer.org/slicerWiki/index.php/Slicer3:Volume_Rendering_With_Cuda">http://www.slicer.org/slicerWiki/index.php/Slicer3:Volume_Rendering_With_Cuda</a>)? I've got Benjamin's code to work before, but his code is far from polished.<br>
<br><div class="gmail_quote">On Tue, May 11, 2010 at 2:26 PM, Francois Bertel <span dir="ltr"><<a href="mailto:francois.bertel@kitware.com">francois.bertel@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Yes you can use the latest DirectX SDK (side note: there are two<br>
DirectX SDK releases per year, one in February, one in August).<br>
<br>
I currently use the Feb 2010 one.<br>
<br>
Once your done building VTK, run the test TestGPUInfo in verbose mode<br>
to see if the returned information makes sense:<br>
<br>
For example, on Vista 64 SP1 with a nVidia Quadro FX 3600M, 512MB, I have:<br>
<br>
> cd vtk-build<br>
> ctest.exe -R TestGPUInfo -V<br>
...<br>
160: Test command: C:\vtk-build\bin\Debug\RenderingCxxTests.exe<br>
TestGPUInfo -D C:/VTKData -T C:/vtk-build/Testing/Temporary -V<br>
Baseline/Rendering/TestGPUInfo.png<br>
160: Test timeout computed to be: 1500<br>
160: There is 1 GPU(s).<br>
160: GPU 0:<br>
160: dedicated VRAM=495 MB<br>
160: dedicated RAM=0 MB<br>
160: shared RAM=1791 MB<br>
1/1 Test #160: TestGPUInfo ...................... Passed 0.13 sec<br>
...<br>
<br>
You can see that 495MB is less than 512MB. This is probably the</blockquote></div><br></div>