Is there a working version of SlicerVR with Segment Editor?

Hi, I followed SlicerVR development updates through previous GitHub issues and NA-MIC project weeks. The in-VR widget seems to have had problems for a long time. Is there any specific previous version/commit/branch of SlicerVR that can access the Segment Editor in Slicer3D, and modify the segment in VR with controllers? We specifically want to use the Paint functionality in VR for manual correction.

If not, what would be the complexity of fixing this feature if we want to try it ourselves?

I confirmed that flying and grabbing the object functions work with Oculus Quest 2 using the commit “Rename VR interactor style callback functions”.

Thanks.

Infrastructure for displaying Qt widgets in immersive views is now in place, but I don’t think any modules have taken advantage of it yet.

I know that @cpinter and others have been planning to work on this, but I don’t think there is dedicated funding for it, so the progress may be very slow.

It would be great if you could work on it. To get started, you can build Slicer and the SlicerVirtualReality extension and try to display a vtkQWidgetWidget in Slicer.

How did you set up the Oculus/Meta Quest 2 headset to be accessible from Slicer?

I have built the Slicer version 5.3.0-2023-02-27 from the source code. Then, built the SlicerVR using this commit: “Rename VR interactor style callback functions”.

  • Copied the json files as discussed in this topic to make controllers work.
  • Connected the Quest 2 headset to the PC using a cable and Oculus PC app.
  • In the Quest 2, opened the Oculus Link from the menu and went to the Virtual Desktop.
  • In the PC, launched the SteamVR.
  • In the PC, opened the Slicer, loaded my volume and segmentation data, and clicked the headset icon on the top left.
  • Finally, it started the application through the SteamVR.

I can see my controllers, fly around, grab and transform my segmentation (could not grab the volume). I can also see the volumes, but they disappear if I get close. Seems like volumes might have some clipping issues.

5 Likes

I can confirm there is (at least was not long ago) a clipping issue with volume rendering in VR. There is no direct issue about this in the repository (although really falls under this one but not mentioned there either Address issues related to integration with VTK 9.1 · Issue #91 · KitwareMedical/SlicerVirtualReality · GitHub). Feel free to open a new issue for this. The Kitware team is working on related things as their capacity allows.

FYI I personally am most interested in the two-handed interaction and the in-VR widget. I will try to revive the two-handed interactions but my free time is very limited.

1 Like