MantisBT - ParaView
View Issue Details
0010557ParaViewBugpublic2010-04-15 14:312016-08-12 09:58
Ken Moreland 
Robert Maynard 
normalminorhave not tried
closedmoved 
 
 
0010557: Structured volume rendering broken on tiled displays
(From Liu Ning on the ParaView mailing list.)

There seems to be a problem with the volume rendering of image data on tiled displays. When rendering on two nodes and two tiles, each tile has half the data (presumably the local half).
No tags attached.
jpg Wavelet-FixedPointMapper.jpg (17,669) 2010-04-15 14:31
https://www.vtk.org/Bug/file/8032/Wavelet-FixedPointMapper.jpg
jpg

jpg Wavelet-GPUMapper.jpg (18,496) 2010-04-15 14:31
https://www.vtk.org/Bug/file/8033/Wavelet-GPUMapper.jpg
jpg

jpg box_ex2.jpg (17,066) 2010-04-15 14:31
https://www.vtk.org/Bug/file/8034/box_ex2.jpg
jpg
Issue History
2010-04-15 14:31Ken MorelandNew Issue
2010-04-15 14:31Ken MorelandFile Added: Wavelet-FixedPointMapper.jpg
2010-04-15 14:31Ken MorelandFile Added: Wavelet-GPUMapper.jpg
2010-04-15 14:31Ken MorelandFile Added: box_ex2.jpg
2010-04-15 14:33Ken MorelandNote Added: 0020194
2010-04-29 15:45Utkarsh AyachitNote Added: 0020482
2010-04-30 14:30Utkarsh AyachitStatusbacklog => tabled
2010-04-30 14:30Utkarsh AyachitAssigned To => Robert Maynard
2010-04-30 14:30Utkarsh AyachitTarget Version => 3.10
2016-08-12 09:58Kitware RobotNote Added: 0037810
2016-08-12 09:58Kitware RobotStatusexpired => closed
2016-08-12 09:58Kitware RobotResolutionopen => moved

Notes
(0020194)
Ken Moreland   
2010-04-15 14:33   
My guess is that the problem is with the representation proxy responsible for volume rendering image data. The problem appears to be independent of the image data volume renderer (see the attached images of the Wavelet rendering with two different mappers, both of which are broken). When you render, for example, an unstructured grid (such as in the attached image of box.ex2), it renders fine.
(0020482)
Utkarsh Ayachit   
2010-04-29 15:45   
The problem is because the by default paraview does not use compositing on tile-displays for small data. We support movement of polydata/unstructured grid, so they are happily cloned on all tile machines and hence volume rendering works. But with image data, we don't move the data around and hence the volume rendering looks broken.

Setting "Compositing Threshold" to 0 under the Tile Display Parameters does the trick.

However this is a nuisance. As a fix, the tile display view should automatically detect if volume rendering is being used and force a compositing mode.
(0037810)
Kitware Robot   
2016-08-12 09:58   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.