Hi:
I configure my oculus rift in my notebook. The games runs perfectly. Then, I install 3D slicer (version 5.2.2. in Windows) with VR extension, but when I select the VR glasses icon in 3D Slicer, in some seconds appears a red cross over it?. Why?
Sincerely,
Gonzalo Rojas Costa
Unfortunately, the VR extension of 3D Slicer is still broken. All my recent tests with the Oculus Quest2 failed with 5.x Slicer versions. The last working session I can remember was with 4.11.
Do you know if exist any idea to upgrade it for 3D Slicer 5.x ?
@rbumm Can you please share detaills about how it is broken? It works for me in 5.3 except the two-handed gesture.
The one issue is you have to copy the manifest json files manually next to the Slicer executable. @jcfr I’m not sure, do we have some guidelines about it or any way to make this easy for the user?
That’s correct! The Oculus Quest 2’s right-handed joystick allows you to manipulate objects in 3D space. By using the joystick, you can move the object around, and you can adjust the direction of movement by tilting the right controller.
To ensure proper functionality, one must make sure that the manifest JSON files are located in the same directory as the Slicer.exe file.
In version 4.11, you could grab an object by simultaneously pressing both grab triggers, and then rotate and tilt the object as desired. However, this feature is currently broken in version 5. When attempting this action, the object disappears from the 3D space.
What you could grab in 4.11 was the “world” and not the object, this is an important difference from what you say. So the object stayed the same in RAS, but the camera and the scaling of the world changed (just try it with multiple objects in the scene and you’ll see).
That said, I miss this feature very much, because it is super convenient to navigate that way. I don’t have funding for this, and unfortunately also don’t have free time these months, so the same as you, I can only wait. However, I’m trying to be present in the efforts that do have funding (although it is targeted only tangentially because it’s for AR), and whenever I see that I have a day to work on this I’ll coordinate with them and get this done finally.
Ok, I understand. Do you know where the camera position adjustment is made in the Slicer VR source code and which VTK function would be responsible for moving the camera?
You can find the details of our findings on this page, and at the links pointed from it: ProjectWeek/README.md at master · NA-MIC/ProjectWeek · GitHub
Basically where this two-handed gesture is managed is the RecognizeComplexGesture function (mentioned in some of the pull requests referenced). The setting of the camera transform as I remember was in the VR interactor style class. If you want further details please don’t hesitate to ask.
From a clinical point of view it would be absolutely great to have a ROI based crop tool for volume renderings and segmentation in VR.
You used 5.3 version with which glasses? Oculus Rift? Because we are trying to configure our Oculus Rift with 5.3 version, and it doesn’t works.
I don’t have an Oculus Rift anymore, I tried HTC Vive Pro and HP Reverb 2. I still don’t know what it means for you exactly that “it doesn’t work”. Some detailed information, hopefully screenshots would be useful.
one must make sure that the manifest JSON files are located in the same directory as the Slicer.exe file.
The associated issue [1] has been fixed[2] in the SlicerVirtualReality project.
To support configuring the the folder in which the action manifest files are located, the relevant fix from upstream VTK were integrated in our Slicer/VTK fork[3].
Question: Could someone try to download the latest preview build of Slicer and try the SlicerVirtualReality extension ?
Downloaded the latest preview build of Slicer and installed the SlicerVirtualReality extension.
With or without the JSON files the segmentation is shown in the headset, but none of the keys for manipulation work (joystick, grab etc) But grabbing with both controllers does not let the object dissapear from the scene.
This was tested with the Quest 2 (it shows a Rift connection) but on an older PC with a GTX 970, still in quite good shape, I will try 4.11 next just to make sure the system generally works.
4.11 works well on that old system and has all interaction keys active (joystick and both grab triggers).Sidenote: Exiting VR (SteamVR) crashes Slicer.
Same here with the latest preview. Without copying the jsons I get this, and no interactions work. I didn’t try copying the file as I understand the goal was to check if it works without manual copying.
Thanks for working on this @jcfr !
Interestingly, in my case, I did not get this missing action manifest message in SteamVR this time without the JSONS. On a second try with the JSONS, at least one of the buttons seemed to work (the “B” left controller menu button).
