Hi,
thanks for the hints, we didn't look into these VTK classes yet, but we are very curious about speeding up and improving 2d image rendering. :) The 2d image mapper is a "hot" topic anyways for years (see https://phabricator.mitk.org/T24071 for example). It also has fundamenal flaws regarding pixel-perfect rendering as every image in the scene is mapped into a common single texture instead of separate sprites. Unfortunately, the mapper is one of the most core and complex/historically grown components of MITK and substantial amount of time is necessary to rewrite the whole thing without breaking compatibility and certain not so obvious features. I cannot promising anything regarding time but sooner or later we must take care of it. Cheers, Stefan ________________________________ Von: Federico Milano <fmil...@gmail.com> Gesendet: Freitag, 10. April 2020 19:44 An: mitk-users@lists.sourceforge.net Betreff: [mitk-users] Plans for migrating 2D image mappers to vtkImage(Re)SliceMapper Hi. I wanted to know if you have any long term plans for migrating the current mitkImageVtkMapper2D from mitkExtractFilter & vtkImageReslice to the vtkImageSliceMapper/vtkImageResliceMapper + the vtkImageSlice actor. My motivation for asking this is that I have found that the reslicing is very optimized in vtkImageReSliceMapper and in my measurements it seems to be working faster than the mitkImageVtkMapper2D. I have implemented a POC of a new mapper using vtkImageSlice as the actor, and the problem that I find is that I cannot control well the layer of the slice, so I cannot blend it correctly with other images or surface contours. I suppose I should use vtkImageStack, but I have to modify other parts of the MITK architecture to integrate that actor. What are your thoughts about this? Thanks! Federico
_______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
