Porting to Oculus Rift S

LastBlow 2019-10-28 21:42:41 UTC #1

Porting a Leap Motion/Oculus Rift app (Windows 10, C++, Leap Motion SDK Orion 3.2.1 and Oculus Rift SDK Commercial version 1.25.0) from DK2 to Oculus Rift S... Any advice in general? Any experience with Oculus Guardian in particular - how to turn it off if using desktop Leap Motion or head-mount Leap Motion and define the floor level at mid-height, so objects lying on the terrain can be reached while standing without constantly crouching down? Thank you!

AlexColgan 2019-10-30 20:28:38 UTC #2

Is this an Unreal application?

LastBlow 2019-10-30 20:42:28 UTC #3

Good to hear from you, Alex! No, standalone app. Windows 10, C++, Leap Motion SDK Orion 3.2.1 and Oculus Rift SDK Commercial version 1.25.0.

AlexColgan 2019-10-31 01:33:43 UTC #4

Standalone? Unless you're upgrading to the V4 Leap Motion SDK, I don't have any solid advice to give.

LastBlow 2019-11-01 00:09:19 UTC #5

Definitely planning to upgrade to the V4 Leap Motion SDK. What would be your advice then? Again, in general and concerning Oculus Guardian in particular - how to turn it off if desktop-mount Leap Motion or how to define the floor level at mid-height if head-mount Leap Motion, so objects lying on the terrain can be reached while standing without constantly crouching? Thank you!

AlexColgan 2019-11-03 03:21:55 UTC #6

The floor level is something that can be set independently of any Leap Motion assets, since it has more to do with defining the distance between the floor and the headset within the scene. The only thing you need to do that would be Leap Motion-specific would be ensuring that the virtual controller within the scene is a child of the virtual headset, and that the VR tracking mode flag is enabled.

LastBlow 2019-11-03 04:53:41 UTC #7

Thank you, Alex. Alright, here comes the crime scene...

First updated to the latest Oculus Rift SDK 1.41.0. The scene rendered in VR 90 degrees to the right with interaction box and stable hands. Then updated to Leap Motion SDK 4.0.0, the scene rendered again 90 degrees to the right but this time with no interaction box and unstable hands. For some reason, the Leap Motion interaction box is not rendered anymore or probably rendered somewhere where I can not see it!

On another note, still only one hand shows in the Oculus Rift split-screen. Please, see this other post before SDK's updates where the scene is rendered in front using a DK2 with 2 interaction boxes, one to the left and one to the right, but only one hand to the left: https://forums.leapmotion.com/t/hand-in-left-split-screen-only/8300.

Just to confirm, when you say "make sure the VR tracking mode flag is enabled", you mean setting the controller policy, right, as in: m_controller.setPolicy(static_cast(Leap::Controller::POLICY_OPTIMIZE_HMD | Leap::Controller::POLICY_IMAGES));

The code has not been changed at all. Any idea what is going on, please?

AlexColgan 2019-11-03 13:12:39 UTC #8

Interaction box is no longer supported. Can you let me know what you mean by unstable hands?

Given that your plugin is entirely custom and in a custom environment, it's very hard to say why the hands would be rendering in one eye but not the other.

You're correct about the flag.

LastBlow 2019-11-04 02:04:46 UTC #9

Any explanation why the interaction box is not supported anymore? It was a neat feature visually showing the hands outreach! Will probably end up programming it myself as a training tool.

So, I understand there is no particular reason in the Leap or Oculus SDKs as to hands render in one half-screen but not in the other. Will have a look at the code once again, keep you updated.

Finally, used for now ovr_RecenterTrackingOrigin(m_ovrSession); to recenter the scene in front. Will see with Oculus why would the scene end up rendered 90 degrees to the right in the latest SDK.

AlexColgan 2019-11-04 12:30:11 UTC #10

The Interaction Box is no longer supported because it was more a tool for desktop than VR use, and had some abstraction built into it that proved less relevant over time as we moved away from gestures. A utility that describes the active interaction range would be better expressed as an inverted pyramid.

In the case of head-mounted VR applications, the Leap Motion Controller's FOV typically extends beyond the headset's FOV. If a user is able to see their hands, they can use them to interact with virtual content.