I figured out that at least one opaque image has to be present. If you set the opacity of the image (e.g. pic3d) to anything else then 100% the color will be applied correctly to the binary image. Furthermore, any property change (not only opacity) of the binary image will make the color disappear until the next renderwindow update.

This bug is somehow related to VTK rendering calls. If you outcomment the switch in the mitkVtkProprenderer (l. 219++):

switch(type)
{
case mitk::VtkPropRenderer::Opaque:        mapper->MitkRenderOpaqueGeometry(this); break;
case mitk::VtkPropRenderer::Translucent:   mapper->MitkRenderTranslucentGeometry(this); break;
case mitk::VtkPropRenderer::Overlay:       mapper->MitkRenderOverlay(this); break;
case mitk::VtkPropRenderer::Volumetric:    mapper->MitkRenderVolumetricGeometry(this); break;
}

every VTK method for rendering will be executed always and as a result the bug is gone. However, this is too much overhead. We have to figure out why the specific method (I assume MitkRenderTranslucentGeometry()) is not called in this combination of objects in the DataStorage.

We figured out that this is a Linux only issue.

Thomas what is the status of this bug? Is it possible to fix it for the upcoming release? If not please change Target Milestone.

I have no idea what is actually going wrong. This could be related to the recent work of Daniel regarding the opacity of the texture. I will talk with him about it. Anyway it is just on Linux.

I talked to Daniel with this and he also has no idea what could be the reason for this special case.

Since this is only for contours, only on linux, only when other pictures are involved and only when the opacity is changed, I will put this on won't fix.