Create two binary images and enable on both volume rendering, only one of them is rendered instead of both...
Description
Status | Assigned | Task | ||
---|---|---|---|---|
Wontfix | kislinsk | T10862 RDF: Volume rendering of multiple segmentations and cross hair | ||
Resolved | None | T10174 Provide opacity property for first color in Lookup Table | ||
Resolved | None | T8165 Improve performance of ImageVtkMapper2D |
Event Timeline
In the current release, this is different. I cannot reproduce your reported behavior, however, if I disable the cross hair, only the first segmentation is shown in volume rendering which is a major loss of function.
The problem seems to be that result segmentation rendering is surrounded by a black box, which hides the other segmentations. All objects with a layer higher than the first segmentation are hidden.
If a second images is loaded and rendered (with lower layer than the segmentation) it is also (partly) hidden behind the segmentation.
So this is a general rendering issue, since "empty" voxels are rendered as solid black voxels instead of opaque voxels.
See attached screenshots.
What is the status of this bug? Please change the target milestone to "AfterNextRelease" if this bug is not relevant or cannot be fixed in time for the 2013-06 release.
This bug could not be fixed for release 2013-06. Setting target milestone to next release
Interestingly the volumerenderings works with the CPU rendering options. The GPU options show only the segmentation with the lowest layer-value.
At the moment it is not possible to volume render more than one binary image. There are two possible solutions:
- merge the binary images and render the merge image
- wait for the multilabel binary images ( several segmentations saved as one image )
The problem is that a binary image is as big as the original image with transparent color.
How important is this for you? Could you adapt severity and importance, if necessary?
I don't know how important this is and if we should urgently spend resources to fix it. Can someone of the segmentation group please give a comment?
I would suggest to wait for the multilabel stuff. This bug will most likely not be fixed within the next week, so I will change the target milestone.