Hi all, Hi Peter,
We finally found the problem. It seems that the only major differences,
apart from the shader in 2D, is this line:
vtkSmartPointer m_FiberAssembly;
// adding the m_FiberActor and retuning it in GetVtkProp()
We're not exactly sure how adding a vtkPropAssembly fixes the problem
Hi all, Hi Peter,
I've been using the mitk::FiberBundleXMapper2D and 3D in our program and
I found a really strange behavior. I searched all day, to no avail. For
the same data (a polydata at the same adress in memory), my lines are at
different positions in my mapper (or at least *seen* at di
