BUG in vtkFixedPointVolumeRayCastMapper
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
There are some int overflow bugs in vtkFixedPointVolumeRayCastMapper, if used with big volumes [2000 * 2000 * 2000] > [max(int) = 2147483647] and shading enabled.
BUG 1: Line 2787 / 2788 int sliceSize = dim[0]dim[1]((independent)?(components):(1)); int numSlices = dim[2]; should be: vtkIdType sliceSize = dim[0]dim[1]((independent)?(components):(1)); vtkIdType numSlices = dim[2]; because of line 2840, 2848, … where the actual int overflow happens (numSlices * sliceSize)!
BUG 2: Line 98 int x, y, z; should be: vtkIdType x, y, z; because of line 171, where the actual int overflow happens (dptr = dataPtr + z * dim[0] * dim[1] + y * dim[0] + xlow;)
Attached to this bug report you will find the fixed version of vtkFixedPointVolumeRayCastMapper.cxx.