Loading MRB file breaks linked views

This issue can be replicated using by the following steps:

  • load MRIHead and render in Dual 3D
  • save as an MRB file
  • reopen Slicer, load MRB file
  • use link/unlink buttons in 3D view windows to link views

The viewers cannot be linked. When the MRB file is loaded, 2 additional cameras are loaded and associated with the 3D views. The link problem can be resolved by deleting one or both of these cameras:

c1=slicer.mrmlScene.GetNodeByID(‘vtkMRMLCameraNode1’)
c2=slicer.mrmlScene.GetNodeByID(‘vtkMRMLCameraNode2’)
c3=slicer.mrmlScene.GetNodeByID(‘vtkMRMLCameraNode3’)
c4=slicer.mrmlScene.GetNodeByID(‘vtkMRMLCameraNode4’)
slicer.mrmlScene.RemoveNode(c3)
slicer.mrmlScene.RemoveNode(c4)

Deactivating these same cameras, or associating cameras 1 and 2 with the 3D views does not have an effect. Any insight on how the cameras/views are working would be appreciated. If this is not a known issue, I can start a bug report.

1 Like

I have a similar problem and I am wondering if it is a known issue.
I usually save MRB files when I am working on a complex visualization. However, if I have double 3D views with different volumes rendered in each, loading the saved MRB file does not setup the same render options. I often end up having both volumes rendered in View1. There is no data loss but the volumes, fiducials and segmentations that are set to be rendered in View2 window are all back in View1 and it defeats the purpose of setting everything nicely and saving an MRB.

1 Like

We have an issue in the bugtracker for this, scheduled to be fixed in Slicer5 (planned within a few weeks). What you experience might be related, so please add it as comment to the issue:

2 Likes