Surface mesh with opacity different of 1 is not rendering properly when changing the Zoom of the 3D view
When changing this line of code in QVTKWidget.cpp, Ln 242:
//if(isVisible()) { this->mRenWin->Start();
...
Then it works
xplanes | |
Feb 15 2010, 7:04 PM |
F463: head_100cm_dec_neu.stl.zip | |
Jan 11 2012, 4:30 PM |
F462: Snapshot_DepthSorting.PNG | |
Nov 30 2011, 5:48 PM |
F461: NoDepthSorting.png | |
Nov 30 2011, 5:40 PM |
F460: render2.JPG | |
Feb 15 2010, 7:06 PM |
F459: render1.JPG | |
Feb 15 2010, 7:05 PM |
Surface mesh with opacity different of 1 is not rendering properly when changing the Zoom of the 3D view
When changing this line of code in QVTKWidget.cpp, Ln 242:
//if(isVisible()) { this->mRenWin->Start();
...
Then it works
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | None | T9898 Metabug: Revise MITK Surface Rendering | ||
Wontfix | None | T3345 Surface mesh opacity problems |
Resetting all bugs without active assignee flag to "CONFIRMED". Change status to IN_PROGRESS if you are working on it.
we fixed another bug related to transparency by using a depth sorted polydata. This special rendermode can be enabled by setting the bool property "Surface Rendering.Depth Sort".
Maybe this fixes also your rendering bug, xplanes?
You can check out this branch "bug-3345-meshopacity" to test it.
I wrote the core change request. Anja will provide a screenshot of the depth sorted surface.
We figured out that depth peeling is disabled by default. As a result, there is no connection between the bug and depth peeling.
We also implemented a small example in VTK (without MITK) reproducing the bug on my machine. We have to test this on other OS and hardware.
We tested the "stl causing the issue" STL surface on the following systems with MITK and a simple VTK example application (see comment above - ReadSTL). Our results so far are:
We tested again. Under windows everything is fine. Needs to tested again under Mac and Ubuntu.
It is still awful in ubuntu 12.04..
We should decide whether we want to investigate more here or keep this as known issues caused by VTK only on linux.