VTKEdge:FAQ: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
Line 16: Line 16:
* Example of driver version with the fix: nVidia Quadro FX 3600M, Driver, Windows Vista 64-bit, Multi Language, Precision M6300, v.175.75 ISV, A01. Release Date: 6/10/2008
* Example of driver version with the fix: nVidia Quadro FX 3600M, Driver, Windows Vista 64-bit, Multi Language, Precision M6300, v.175.75 ISV, A01. Release Date: 6/10/2008
* References: http://developer.nvidia.com/forums/index.php?showtopic=596 http://www.stevestreeting.com/2007/12/27/nvidia-16921-driver-bug-in-glsl/
* References: http://developer.nvidia.com/forums/index.php?showtopic=596 http://www.stevestreeting.com/2007/12/27/nvidia-16921-driver-bug-in-glsl/
== TestKWEGPUArrayCalculator ==
=== time out on Vista ===
Depending on how fast/slow is the graphics card, the computation on the GPU can take more than 2 seconds. On Vista, after a 2 seconds timeout, the Windows Vista's Timeout Detection and Recovery (TDR) kills all the graphics contexts, resets the graphics chip and recovers the graphics driver, in order to keep the operating system responsive.
ref: http://www.opengl.org/pipeline/article/vol003_7/
This reset actually freezes the test. And it really time out this time...

Revision as of 20:32, 25 November 2008

Requirement

Compile time

Run time

  • The volume mapper works with nVidia cards from GeForce 6 series (or Quadro equivalent) and above
  • The LIC algorithms work with nVidia cards from GeForce 8 series (or Quadro equivalent) and above

Issues

vtkKWEGPUVolumeRayCastMapper

fatal error C9999: Bad scope in ConvertLocalReferences()

This is an nVidia bug. It has been fixed by nVidia. Just update your driver.

TestKWEGPUArrayCalculator

time out on Vista

Depending on how fast/slow is the graphics card, the computation on the GPU can take more than 2 seconds. On Vista, after a 2 seconds timeout, the Windows Vista's Timeout Detection and Recovery (TDR) kills all the graphics contexts, resets the graphics chip and recovers the graphics driver, in order to keep the operating system responsive.

ref: http://www.opengl.org/pipeline/article/vol003_7/

This reset actually freezes the test. And it really time out this time...