This might be an issue for Alex to look at.

Crash fixed in r19382:
http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=19382

(please create another issue for the FOV pb)

There are still a few small things:
-Presets do not get populated on restore
-On loading a scene, the master view does not set the
FOV properly (it does, when just restoring a sceneview)
-the sceneviews do not bring up the module which was visible when the sceneview was created.

-no presets: Ok, I'll investigate.
-bad fov on loading -> Jim (I believe he already has issues assigned to him for that)
-restore module in sceneview -> feature request, can you create a separate issue . It needs to be discussed as scene views restore the "scene" (or data), not the "state" of the application (current module).

I am not sure to understand the problem with the presets.
Can you please describe a step by step scenario.

The presets are being set properly in mac nightly 5-8. Restoring the sceneviews works as well.

This is still not working properly. When I opened the scene, I do not see anything in the 3d viewer. When going to the VR module, the volume visibility is off.

the screenshot I just added was taken with 4.1.1. nightly, 7-03

This is still the status. Its still broken

What are the plans?

Fixed in r20911:
http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=20911

Its still not working on mac nightly 9-15. Attaching a screen shot after restoring sceneview 4

Please create a new MRML scene, the scene in VR-Test-2012-02-22 is no longer supported (or replace in the mrml scene VolumeRenderingParameters with CPURayCastVolumeRendering )

http://na-mic.org/Mantis/view.php?id=2531 is the new scene

The problem is that scene view node (vtkMRMLSceneViewNode) view node (vtkMRMLViewNode) is vtkMRMLViewNode1 and the Volume rendering display node in the scene view points to vtkMRMLViewNode1, but after restore, the 3D view uses vtkMRMLViewNode2.
Therefore the display node can't be visible in the 3D view.

For some reasons, the scene view node (vtkMRMLSceneViewNode1::View1) has its view node (vtkMRMLViewNode) ID changed from vtkMRMLViewNode1 to vtkMRMLViewNode2 but the view node ID is not changed in the volume rendering display node.

Hi Julien -

I believe some of the logic for the view nodes was something copied over from slicer3 but then some fixes were never replicated in the context of slicer4.

http://viewvc.slicer.org/viewvc.cgi/Slicer3/trunk/Base/GUI/vtkSlicerViewerWidget.cxx?r1=15436&r2=15470

IIRC line 1052 was the fix for Sebastien's code about "Stealing unassigned camera nodes".

I don't see problem with the view node logic.
See below what I think the problem is :
In MRML scene:
...
<SceneView id="vtkMRMLSceneViewNode1" name="View1" ...
<View id="vtkMRMLViewNode1" name="View" ...
<NCIRayCastVolumeRendering id="vtkMRMLNCIRayCastVolumeRenderingDisplayNode1" name="VolumeRendering" viewNodeRef="vtkMRMLViewNode1" ...
...
After loading scene:
Here is the content of vtkMRMLSceneViewNode1 (represented as a mrml)
<View id="vtkMRMLViewNode2" name="View" ...
<NCIRayCastVolumeRendering id="vtkMRMLNCIRayCastVolumeRenderingDisplayNode1" name="VolumeRendering" viewNodeRef="vtkMRMLViewNode1" ...

So when vtkMRMLSceneViewNode1 is restored, it keeps vtkMRMLViewNode2 in scene (was already there when loading the scene) but vtkMRMLNCIRayCastVolumeRenderingDisplayNode1 still points to vtkMRMLViewNode1.

The code responsible for changing vtkMRMLViewNode1 to vtkMRMLViewNode2 is vtkMRMLSceneViewNode::UpdateScene(vtkMRMLScene *scene) (done in r8315).
I see 2 options:

• we don't change the ID
• if we change the ID of the view node, we also change it in vtkMRMLNCIRayCastVolumeRenderingDisplayNode1

Scene views fixed in r21027

However the volume rendering is now broken when importing the scene.
This is because the imported view node has its ID changed (vtkMRMLViewNode1 to vtkMRMLViewNode2) because there is already an existing view node (vtkMRMLViewNode1). However, only the vtkMRMLViewNode1 is mapped into a widget (it would work if you show the two 3D views), and the volume rendering display node is only visible in the vtkMRMLViewNode1 which is changed to vtkMRMLViewNode2.

See 0001887 (esp. comment 0004004)

Fixed in r21033:
http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&amp;revision=21033

Master scene view is correctly restored on import.
Views are now singletons.

the VR test in rons examples is not working, but when I created a new scene with sceneviews that worked nicely. Can I remove the directory called VR Test from Rons examples?