stevenfour/OculusSdk · Datasets at Hugging Face

text stringlengths 0 1.11k

Set ShowState

Under Project, search for OVRControllerPrefab.

Drag OVRControllerPrefab from the search results onto LeftControllerInHandAnchor.

Under Hierarchy, select OVRControllerPrefab.

Under Inspector, make sure Controller matches the hand, and set Show State to Controller In Hand.

Anchor setup for controllers

Repeat steps 6 through 9 for RightControllerInHandAnchor.

Under Project, search for OVRHandPrefab.

Drag OVRHandPrefab from the search results onto LeftHandOnControllerAnchor.

Under Inspector, make sure Hand Type matches the hand, and set Show State to Controller In Hand.

Anchor setup for hands

Repeat steps 11 through 13 for RightHandOnControllerAnchor.
Prefab changes

OVRControllerHelper and OVRHand both now contain an enum of ShowState: The available options for that are:

Always: The object will not be automatically disabled based on controller and hand state.
Controller in Hand or no Hand: This means this object will be disabled if the controller is not in the user’s hand, or if hand tracking is disabled entirely.
Controller in Hand: This means the object will be disabled if the controller is not currently in a user’s hand.
Controller Not in Hand: This means the object will be disabled if it is in a user’s hand. This is used for the detached controller situation. I.e. sitting on a desk.
No Hand: This will disable the rendering of the object if hand tracking is enabled and there is a hand.
OVRControllerPrefab: OVRControllerHelper

Show State
When Hands Are Powered By Natural Controller Poses: This is a checkbox that controls if the controllers can be rendered even if the hand poses are in the natural state. This is used for the detached controller state.
OVRHandPrefab: OVRHand

Show State
New anchors for the MultiModal feature

LeftHandAnchorDetached and RightHandAnchorDetached: These anchors are for use for controllers that are not in the user’s hand when the Simultaneous Hands and Controllers API is enabled. The default CameraRig prefab does not contain controller prefabs under these anchors so they will need to be added to be used. The show state of these prefabs should be set to “Controller Not In Hand”.
Troubleshooting

How can I confirm Multimodal is running on my headset?
Confirm that the detached controller action path is providing data.

Can I evaluate the feature on my headset without changing my code?
No.

Switching between controllers and hands doesn’t work in the sample.
Ensure that you’re running on Quest 2 (with Meta Quest Pro controllers paired to your headset), Quest 3, or Quest Pro.

Using OVRCameraRig -> TrackingSpace to get positions of hands and controllers simultaneously
Due to the object hierarchy on the OVRCameraRig Tracking Space, it is non-trivial to provide the hand data and the controller data simultaneously with the legacy Anchors. This has required us to create multiple new anchors on the Tracking Space and to add gating logic on the controller and hands prefabs themselves on whether or not to render.Use Fast Motion Mode
Unity

All-In-One VR

Quest

The platform for which this article is written (Unity) does not match your preferred platform (Nativa).
Haz clic aquí para ver la página del índice de la documentación para tu plataforma de preferencia.

Fast Motion Mode (FMM), previously known as “High Frequency Hand Tracking”, provides improved tracking of fast movements common in fitness and rhythm apps. It is highly recommended to first test out your title without FMM enabled, and then only enable it if you observe high tracking loss due to fast hand motion. For most apps, the default hand tracking mode should provide the right balance between accuracy and speed.

Benefits of FMM

Improved tracking of fast movements common in fitness and rhythm apps.
Known limitations

FMM optimizations may result in increased jitter which can impact high accuracy interactions such as direct touch or typing.
As fast motion relies on short exposure time, tracking quality is expected to regress in low lighting conditions. It is recommended to remind users to play in a well lit environment.
Compatibility

Hardware compatibility
FMM is supported on Quest 2, Quest Pro, Quest 3, and all future devices.
On Quest 1, enabling FMM will increase hand tracking frequency, but will not result in any further optimizations.
On Quest 2, enabling FMM will result in app downclocking (reduce GPU level 3 → 2).
Software compatibility
Unity LTS 2021 and above
Integration SDK version 55 and above
Feature compatibility
FMM cannot be enabled together with Multimodal.
IOBT/ WMM will not run when passthrough and full body (FBS) are running along with FMM.
On Quest Pro, FMM cannot be enabled together with face tracking, eye tracking, lip sync, or foveated rendering.
Setup

To enable FMM in Unity, follow these steps.

Open your Unity scene.
Under Hierarchy, select OVRCameraRig.
Under Inspector, under Quest Features, in the Hand Tracking Frequency list, select High. There is no difference between High and Max values as both track hands at high frequency.
Troubleshooting

How can I confirm FMM is running on my headset?
To verify your device has FMM enabled, run adb logcat \| grep FMM on a terminal when hand tracking is running on device.

The expected output is NIMBLE: HTEngine: FMM: enabled: true; active:....

Set ShowState

Under Project, search for OVRControllerPrefab.

Drag OVRControllerPrefab from the search results onto LeftControllerInHandAnchor.

Under Hierarchy, select OVRControllerPrefab.

Under Inspector, make sure Controller matches the hand, and set Show State to Controller In Hand.

Anchor setup for controllers

Repeat steps 6 through 9 for RightControllerInHandAnchor.

Under Project, search for OVRHandPrefab.

Drag OVRHandPrefab from the search results onto LeftHandOnControllerAnchor.

Under Inspector, make sure Hand Type matches the hand, and set Show State to Controller In Hand.

Anchor setup for hands

Repeat steps 11 through 13 for RightHandOnControllerAnchor.

Prefab changes

OVRControllerHelper and OVRHand both now contain an enum of ShowState: The available options for that are:

Always: The object will not be automatically disabled based on controller and hand state.

Controller in Hand or no Hand: This means this object will be disabled if the controller is not in the user’s hand, or if hand tracking is disabled entirely.

Controller in Hand: This means the object will be disabled if the controller is not currently in a user’s hand.

Controller Not in Hand: This means the object will be disabled if it is in a user’s hand. This is used for the detached controller situation. I.e. sitting on a desk.

No Hand: This will disable the rendering of the object if hand tracking is enabled and there is a hand.

OVRControllerPrefab: OVRControllerHelper

Show State

When Hands Are Powered By Natural Controller Poses: This is a checkbox that controls if the controllers can be rendered even if the hand poses are in the natural state. This is used for the detached controller state.

OVRHandPrefab: OVRHand

Show State

New anchors for the MultiModal feature

LeftHandAnchorDetached and RightHandAnchorDetached: These anchors are for use for controllers that are not in the user’s hand when the Simultaneous Hands and Controllers API is enabled. The default CameraRig prefab does not contain controller prefabs under these anchors so they will need to be added to be used. The show state of these prefabs should be set to “Controller Not In Hand”.

Troubleshooting

How can I confirm Multimodal is running on my headset?

Confirm that the detached controller action path is providing data.

Can I evaluate the feature on my headset without changing my code?

No.

Switching between controllers and hands doesn’t work in the sample.

Ensure that you’re running on Quest 2 (with Meta Quest Pro controllers paired to your headset), Quest 3, or Quest Pro.

Using OVRCameraRig -> TrackingSpace to get positions of hands and controllers simultaneously

Due to the object hierarchy on the OVRCameraRig Tracking Space, it is non-trivial to provide the hand data and the controller data simultaneously with the legacy Anchors. This has required us to create multiple new anchors on the Tracking Space and to add gating logic on the controller and hands prefabs themselves on whether or not to render.Use Fast Motion Mode

Unity

All-In-One VR

Quest

The platform for which this article is written (Unity) does not match your preferred platform (Nativa).

Haz clic aquí para ver la página del índice de la documentación para tu plataforma de preferencia.

Fast Motion Mode (FMM), previously known as “High Frequency Hand Tracking”, provides improved tracking of fast movements common in fitness and rhythm apps. It is highly recommended to first test out your title without FMM enabled, and then only enable it if you observe high tracking loss due to fast hand motion. For most apps, the default hand tracking mode should provide the right balance between accuracy and speed.

Benefits of FMM

Improved tracking of fast movements common in fitness and rhythm apps.

Known limitations

FMM optimizations may result in increased jitter which can impact high accuracy interactions such as direct touch or typing.

As fast motion relies on short exposure time, tracking quality is expected to regress in low lighting conditions. It is recommended to remind users to play in a well lit environment.

Compatibility

Hardware compatibility

FMM is supported on Quest 2, Quest Pro, Quest 3, and all future devices.

On Quest 1, enabling FMM will increase hand tracking frequency, but will not result in any further optimizations.

On Quest 2, enabling FMM will result in app downclocking (reduce GPU level 3 → 2).

Software compatibility

Unity LTS 2021 and above

Integration SDK version 55 and above

Feature compatibility

FMM cannot be enabled together with Multimodal.

IOBT/ WMM will not run when passthrough and full body (FBS) are running along with FMM.

On Quest Pro, FMM cannot be enabled together with face tracking, eye tracking, lip sync, or foveated rendering.

Setup

To enable FMM in Unity, follow these steps.

Open your Unity scene.

Under Hierarchy, select OVRCameraRig.

Under Inspector, under Quest Features, in the Hand Tracking Frequency list, select High. There is no difference between High and Max values as both track hands at high frequency.

Troubleshooting

How can I confirm FMM is running on my headset?

To verify your device has FMM enabled, run adb logcat | grep FMM on a terminal when hand tracking is running on device.

The expected output is NIMBLE: HTEngine: FMM: enabled: true; active:....