Controller-Driven Hand (Capsense) v66 is broken.

Question

I have been trying to implement Capsense or controller-driven hands for four days, but I have not been successful. Initially, I worked with version 65 of the Meta XR SDK, but nothing seemed to work despite my best efforts.

When version 66 was released, I hoped that the Capsense issues were fixed, so I updated to version 66 and imported the samples from the Meta XR Core SDK. Interestingly, even the sample scene "ControllerDrivenHandPoses" provided by the developers does not work correctly-the hands do not appear.

My goal is to use controllers while displaying hands and their animations simultaneously. Currently, when I use the controller, my hands disappear. Even if I set the hands to always show, they appear but the controllers do not work to move the player.

I am seeking help to resolve this problem. If anyone knows the solution, please let me know.

ryan-at-melcher · Answer

I fixed what I believe is the same issue you are seeing SadraMoghadam: The synthetic hands in the OVRControllerHands prefab are positioned using a local-space pose which does not account for the camera rig moving or rotating. This means the hands will "remain stationary" rather than follow the player as expected.My fix was to make a copy of the HandVisual script, change it's UpdateSkeleton function to use a world-space pose, and use this script in place of the original component.// WorldSpaceHandVisual.cs

// Add a serialized field to reference OVRInteraction's transformer.
[SerializeField]
private TrackingToWorldTransformerOVR _trackingToWorldTransformer = null;

public void UpdateSkeleton()
{
    // ...

if (_updateRootPose)
    {
        if (_root != null &amp;&amp; Hand.GetRootPose(out Pose handRootPose))
        {
            // Original OVR code. This incorrectly uses the local-space pose
            // to position the hands. The result is the synthetic hands do not
            // follow the player's actual controller position as the player
            // moves and rotates.

//_root.position = handRootPose.position;
            //_root.rotation = handRootPose.rotation;

// Fixed code. This transforms the local-space pose to world-
            // space before assigning it to the hands.

Pose worldPose =
                _trackingToWorldTransformer.ToWorldPose(handRootPose);

_root.SetPositionAndRotation(
                worldPose.position,
                worldPose.rotation
            );
        }
    }

// ...
}This solution also required I duplicate the HandVisualEditor script and set it up for the new WorldSpaceHandVisual. (This fix would've been a lot simpler had Oculus made the access level of members in their scripts protected by default!)Here's a gist of my fixed files: https://gist.github.com/ryan-at-melcher/773d3073329134c43a60110e101f0557

TheDaddis · Answer

I've been through this set of problems as well! I actually wanted the identical behaviour of the old Controller-Driven hands (pressing the grip closes the fist entirely - so things can be grabbed more easily).

In the end I updated to v71 of the Meta SDK, and copied over the missing FromOVRControllerHandDataSource.cs script from the previous SDK version I was using, and I was pleasantly surprised to see that it worked! I have fully unpacked the deprecated prefabs I was using, so hopefully it's future-proofed for a little while at least.

mcgeezax4 · Answer

If you are talking about OVRControllerDrivenHands not working in the Unity play mode, then yes that has been an issue since at least v64. I'm not sure if it ever worked since whenever they deprecated OVRControllerHands and replaced with OVRControllerDrivenHands.

Actually it works if you make a full apk build and deploy it to the headset, but not being able to use it in play mode pretty much makes it unusable for a VR app developer. But the fact that it stlil technically works in a build, and that it has been an issue for so long, leads me to believe they don't intend to fix it.

You can drop in the deprecated OVRControllerHands prefab instead and that should work, at least it did when I tried it back in v64, but it uses some older APIs that wont work with some features.

GHSmedia · Answer

With&nbsp;ryan-at-melcher&nbsp;fix the visual hands are correctly placed, but all Interactors are still broken.CafeSingularity&nbsp;what do you mean with "modifying "FromOVRControllerHandDataSource" to reference a world-space pose"?Maybe change&nbsp;Config.TrackingToWorldTransformer.ToTrackingPose(pose) into&nbsp;Config.TrackingToWorldTransformer.ToWorldPose(pose)?This doesn't seem to work.&nbsp; My HandGrabInteractor of Left/Right-ControllerHand are still positioned in wrong place.In addition,&nbsp;FromOVRControllerHandDataSource&nbsp; is flagged as "Deprecated" and Meta suggest to replace it with ControllerHandDataSource... but how to do that is a mistery!

SadraMoghadam · Answer

Thank you for the solution. I have previously tried using OVRControllerHands on version 65, and now on version 66, but encountered a different problem. When I move the player, the hands remain stationary in one position. For example, if I move the player to position (-8, 0, 0), the hands will appear at position (8, 0, 0). Do you know the reason for this issue and how I can fix it? I have tried almost everything to resolve this problem but couldn't identify the source.

Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨

Controller-Driven Hand (Capsense) v66 is broken.

9 Replies

Quick Links

Other Meta Support

Related Content

Features broken in v85.0

Quest 3 Arm broken

Controller driven hands don't trigger custom grab poses in Interaction SDK

Set up controller driven hands v65

Eye Tracking Suddenly Broken