stevenfour/OculusSdk · Datasets at Hugging Face

text stringlengths 0 1.11k
Option 1: Editor
Once you have imported that project into your OVRPlugin package, under Inspector, in OVRManager, check the Wide Motion Mode Hand Poses Enabled box.

Checked WMM hand poses box

In the Quest Features section of OVRManager, set Body Tracking Support to Required.

Body tracking set to required

In Project Settings > Player > Android > Configuration, set the Scripting Backend to “IL2CPP” and the Target Architectures to ARM64.

Setting scripting backend and target architectures

Option 2: C# Scripts
To turn on WMM programmatically, use this function on OVRPlugin:

void SetWideMotionModeHandPoses(boolean enabled);
To query if WMM is running, use this function on OVRPlugin:

bool IsWideMotionModeHandPosesEnabled();
Test WMM via adb

You can also evaluate WMM on your app without the API calls in code, through adb commands.

Before you begin
In PowerShell, or the terminal, run adb devices to ensure adb is installed and the device is discoverable via adb.
You should see a response like this.

```
List of devices attached
230YC56D0S002V device_ \
```
Steps
To enable WMM, before starting the app, run these commands:
adb shell setprop debug.oculus.forceEnablePerformanceFeatures BODY_TRACKING
adb shell setprop debug.bodyapi.allowhandoverride 1
adb shell setprop debug.bodyapi.handoverridetype 3
To toggle WMM fusion logic before starting the app or while you’re in the app:
Off: adb shell setprop debug.bodyapi.handoverridetype 0
On:adb shell setprop debug.bodyapi.handoverridetype 3
Troubleshooting

How can I confirm WMM is running on my headset?
In your headset, you should see improved tracking of hands outside of your headset’s field of view.

Can I evaluate the feature on my headset without changing my code?
Yes, you can test WMM via adb commands to try the feature without changing your code.Use Capsense
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.

Capsense provides logical hand poses when using controllers. It uses tracked controller data to provide a standard set of hand animations and poses for supported Oculus controllers. For consistency, we provide the Oculus Home hand and controller visuals. Capsense supports two styles of hand poses.

Natural hand poses: These are designed to look as if the user is not using a controller and is interacting naturally with their hand.
Controller hand pose: These are designed to be rendered while also rendering the controller. We provide different shapes depending on the controller type. Currently Capsense supports the Quest 2, Quest 3, and Quest Pro controllers.
Benefits of Capsense

Benefit from best in class logical hand implementation and future improvements instead of investing in a custom implementation.
Known limitations

Due to limitations in the current plugin implementation, in Unity, if hand tracking is enabled and the hand is not on the controller, the hand poses will use the hand tracking data.
When using Link on PC, pose data for controllers is unavailable when you’re not actively using them (such as when they’re lying on a table).
In Unity, 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. The gating logic determines if the prefabs should render.
Compatibility

Hardware compatibility
Supported devices: Quest 2, Quest Pro, Quest 3 and all future devices.
Software compatibility
Unity LTS 2021 and above
Integration SDK version 62 and above
Feature compatibility
Fully compatible with Wide Motion Mode (WMM).
Using capsense for hands with body tracking through MSDK will both work simultaneously, but they have a different implementation of converting controller data to hands, so the position and orientation of joints will be slightly different.
Setup

To leverage the TrackingSpace on the OVRCameraRig prefab, you need to add some prefabs.

Open your Unity scene.

Under Hierarchy, add an OVRControllerPrefab as a child of RightControllerInHandAnchor.

Add another OVRControllerPrefab as a child of LeftControllerInHandAnchor.

Add an OVRHandPrefab as a child of RightHandOnControllerAnchor.

Add another OVRHandPrefab as a child of LeftHandOnControllerAnchor.

For each of the four prefabs you just added, under Inspector set Show State to Controller In Hand.

Show State Property set to Controller in Hand

The Show State Property set to Controller in Hand.

Sample scene

Option 1: Editor

Once you have imported that project into your OVRPlugin package, under Inspector, in OVRManager, check the Wide Motion Mode Hand Poses Enabled box.

Checked WMM hand poses box

In the Quest Features section of OVRManager, set Body Tracking Support to Required.

Body tracking set to required

In Project Settings > Player > Android > Configuration, set the Scripting Backend to “IL2CPP” and the Target Architectures to ARM64.

Setting scripting backend and target architectures

Option 2: C# Scripts

To turn on WMM programmatically, use this function on OVRPlugin:

void SetWideMotionModeHandPoses(boolean enabled);

To query if WMM is running, use this function on OVRPlugin:

bool IsWideMotionModeHandPosesEnabled();

Test WMM via adb

You can also evaluate WMM on your app without the API calls in code, through adb commands.

Before you begin

In PowerShell, or the terminal, run adb devices to ensure adb is installed and the device is discoverable via adb.

You should see a response like this.

```

List of devices attached

230YC56D0S002V device_ \

```

Steps

To enable WMM, before starting the app, run these commands:

adb shell setprop debug.oculus.forceEnablePerformanceFeatures BODY_TRACKING

adb shell setprop debug.bodyapi.allowhandoverride 1

adb shell setprop debug.bodyapi.handoverridetype 3

To toggle WMM fusion logic before starting the app or while you’re in the app:

Off: adb shell setprop debug.bodyapi.handoverridetype 0

On:adb shell setprop debug.bodyapi.handoverridetype 3

Troubleshooting

How can I confirm WMM is running on my headset?

In your headset, you should see improved tracking of hands outside of your headset’s field of view.

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

Yes, you can test WMM via adb commands to try the feature without changing your code.Use Capsense

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.

Capsense provides logical hand poses when using controllers. It uses tracked controller data to provide a standard set of hand animations and poses for supported Oculus controllers. For consistency, we provide the Oculus Home hand and controller visuals. Capsense supports two styles of hand poses.

Natural hand poses: These are designed to look as if the user is not using a controller and is interacting naturally with their hand.

Controller hand pose: These are designed to be rendered while also rendering the controller. We provide different shapes depending on the controller type. Currently Capsense supports the Quest 2, Quest 3, and Quest Pro controllers.

Benefits of Capsense

Benefit from best in class logical hand implementation and future improvements instead of investing in a custom implementation.

Known limitations

Due to limitations in the current plugin implementation, in Unity, if hand tracking is enabled and the hand is not on the controller, the hand poses will use the hand tracking data.

When using Link on PC, pose data for controllers is unavailable when you’re not actively using them (such as when they’re lying on a table).

In Unity, 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. The gating logic determines if the prefabs should render.

Compatibility

Hardware compatibility

Supported devices: Quest 2, Quest Pro, Quest 3 and all future devices.

Software compatibility

Unity LTS 2021 and above

Integration SDK version 62 and above

Feature compatibility

Fully compatible with Wide Motion Mode (WMM).

Using capsense for hands with body tracking through MSDK will both work simultaneously, but they have a different implementation of converting controller data to hands, so the position and orientation of joints will be slightly different.

Setup

To leverage the TrackingSpace on the OVRCameraRig prefab, you need to add some prefabs.

Open your Unity scene.

Under Hierarchy, add an OVRControllerPrefab as a child of RightControllerInHandAnchor.

Add another OVRControllerPrefab as a child of LeftControllerInHandAnchor.

Add an OVRHandPrefab as a child of RightHandOnControllerAnchor.

Add another OVRHandPrefab as a child of LeftHandOnControllerAnchor.

For each of the four prefabs you just added, under Inspector set Show State to Controller In Hand.

Show State Property set to Controller in Hand

The Show State Property set to Controller in Hand.

Sample scene