[vtkusers] vtkSmartVolumeMapper in CPU mode stays always in low resolution

[Marc Ruiz Altisent]

Hi,

I have found another bug in vtkSmartVolumeMapper. This time the issue is
that if you set CPU render mode and keep the rest of the mapper settings as
default, when you manipulate visualization the mapper will lower the
resolution to achieve an interactive framerate, as expected, but after the
interaction it stays in the low resolution, which is the bug. It can be
seen easily when visualizing a typical CT dataset for example.

I don't understand the specific cause of the bug, but it doesn't happen if
you disable InteractiveAdjustSampleDistances.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://vtk.org/pipermail/vtkusers/attachments/20180524/e38fb360/attachment.html>