Page MenuHomePhabricator

XRay rendering
Closed, WontfixPublic

Assigned To
Authored By
xplanes
Jan 29 2010, 3:43 PM
Referenced Files
F446: bug3266_1.diff
Jul 5 2010, 9:47 AM
F445: XRAYImage.JPG
Jan 29 2010, 3:46 PM
F444: bug3266.diff
Jan 29 2010, 3:45 PM

Description

Moved the enum definition of transfer functions to mitkTransferFunction.h and added two transfer functions: TF_MR_MIP and TF_XR_VR.

Added vtkMitkOpenglXRAYVolumeTextureMapper2D that is being used by GPUVolumeMapper3D.

To use XRay rendering (based on example Step3.cpp):

// Set these two properties to true
node->SetProperty("volumerendering", mitk::BoolProperty::New(true));
node->SetProperty("xrayvolumerendering", mitk::BoolProperty::New(true));

// Use this transfer function
mitk::TransferFunction::Pointer tf = mitk::TransferFunction::New();
tf->SetTransferFunctionMode( mitk::TransferFunction::TF_XR_VR );

// Set background to white
renderWindow.GetRenderer()->GetVtkRenderer()->SetBackground( 1, 1, 1 );

Event Timeline

xplanes added a subscriber: xplanes.

Unified patch

XRay rendering using Step3.cpp

XRAYImage.JPG (533×574 px, 16 KB)

Markus, I think you already thought or worked on something like this?

Extended mitkGPUVolumeMapper3D with vtkImageResample

Resetting all bugs without active assignee flag to "CONFIRMED". Change status to IN_PROGRESS if you are working on it.

We reviewed the patch and came to the conclusion XRay Rendering would be nice in MITK, but the implementation provided by xplanes is based on the vtkVolumeTextureMapper2D, which uses out of date rendering techniques.
Setting this bug to RFD, if it is necessary at all and if it is adaptable to the today available mappers.

This is a feature request of minor importance right now.

kislinsk claimed this task.
kislinsk added a subscriber: kislinsk.
This task was automatically closed because it wasn't updated at least since July 2016 (over 2 years). Please re-open this task if you think that it is still relevant. This most probably means that you will resolve it.