Unnecessary collection when rendering bounding box LOD
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
When in client/server mode, there is a special LOD that renders a bounding box on the client rather than rendering real geometry. The intention is that regardless of latencies, bandwidths, and data size you should be able to render this bounding box with no problem.
However, I have noticed that the first time you do an interactive render with the bounding box, there is still an odd pause. To replicate, do the following.
- Start ParaView client/server (or multi-core mode).
- Check settings Render View -> Server -> Client Outline Threshold is on and about 100 MBytes (the default).
- Create a Wavelet source, whole extent [-100,100] along each axis (yeah, big). Apply.
- Add contour. Delete default isosurface value, click New Range, Click OK for defaults, Apply. The resulting surface is about 110 MB.
- Drag in the 3D view to render. You will notice a pause before the bounding box is rendered at a new camera angle.
If you monitor the Timer Log carefully, you will notice that during the interactive render there is some gathering of information that occurs. There is no reason to collect any information when rendering the bounding box.