vtkSmartVolumeMapper in CPU mode stays always in low resolution
Hi,
I have found an issue in vtkSmartVolumeMapper. 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. It also doesn't happen in GPU render mode.
I have attached an example where this happens (it's based on the SmartVolumeMapper example from the VTK examples page). If you run it without arguments and maximize the window you will observe the issue after moving the camera.