v62 ControllerDrivenHands broken?

I am also facing the same issue any help will be appreciated!

I am also updated to V64!

Hey ya'll, so DNightOwl's fix didn't work for me, and the hand examples still seem to broken in-editor and build. As far as I can tell, this is still an active issue, so you're not alone. I've put the hand animation on backburner for now as I work on other aspects of the project.

Just fyi, I'm still experiencing the same problem in v67. I would like to update my app with the latest SDK, but I can't debug it if I can't see the controller driven hands.

Digging into the bug a little deeper it looks like the hand data it gets when switching to controllers does not look valid. As a result it disables the SkinnedMeshRenderer on the controller hand models.

Since Meta seems to have no interest in fixing this, has anyone else dug deeper than just seeing the skinned mesh renderer never gets turned on?  I tried but now I am even more confused than before. 

I compared OVRControllerDrivenHands to OVRControllerHands, which was the previously working controller hands solution but is now deprecated.  That deprecated prefab has a script FromOVRControllerHandDataSource which pulls from the controller input and generates a HandDataAsset for the Hand to use, doing things like converting the controller trigger value to a hand pinch value.  But the newer OVRControllerDrivenHands doesn't seem to have anything like that.  In fact as far as I can tell it's just set up to show controllers when you pick them up, or use hand tracking and show hands when controllers are set down, and nothing more.

The deprecated FromOVRControllerHandDataSource does say to use ControllerHandDataSource instead, which does similar controller input to hand data mappings, but why is this script not anywhere in the OVRControllerDrivenHands prefab?  I did my best to learn how DataSource and DataModifier work, and tried to add that script into the prefab myself, and I did get the data flowing all the way to the hand visual and the skinned mesh renderer was supposedly on, but I still didn't see the hands appear.  For the record, the flow was: FromOVRControllerDataSource -> Controller -> ControllerHandDataSource -> Hand -> Synthetic Hand -> Hand Visual.

If anyone has or is willing to dive into this deeper I'd love to hear some other thoughts about attempts to resolve this or clarification about stuff I may be misunderstanding. Or specifically if someone has some insight into the DataSource/Modifier system that is responsible for passing data around, I'm still not entirely sure I understand it beyond just Update After Previous Step is for receiving notification from the previous step that new data is available, and Data Modifer is for passing/modifying the data when something else requests it with GetData.

Of use and request confusion on where to get the samples (find them in the 'Samples' tab, for each package in the Package Manager window - it then adds them to Assets/, not Packages/), it seems that I can't get my controller-driven hands of the service to get the vista 

Same Problem In V67, I just wanna try the tutorial to vibrate conrtoller, still not fix it. ControllerDrivenHands still are controllers not synthetic Hands

Yes, "Developer Runtime Features" are enabled. The Problem still persists.
Even in the SampleScenes (v67) the Synthetic hands are not visible when testing in the Unity Editor. You can only see the controllers, but cannot grab anything.
It only works in build for me.

I tested multiple scenes (in Editor via Link Cable) that have a version of the ControllerDrivenHands in their Rig (Gesture, Handgrab, HandgrabUse, Snap) in a new Project (ISDK v68, Unity v2022.3.15f1) - I can not see the synthetic hands anywhere and the controllers that are shown in the latter 3 scenes cannot perform any function (grabbing, use...).

1.  Create the Unity project
2. Switch build target to Android
3. Install Meta XR All-in-One
4. Install Unity XR support
5. Enable Oculus XR plugins for both Android and Windows
6. Run the Meta > Tools > Project Setup Tool and apply all recommended fixes
7. Install the Interaction SDK Example Scenes
8. Open the GestureExamples scene
9. Start Link (with cable) from Quest 3
10. While holding controllers, press Play in Unity

•  In the OVRManager, ensure that the "Controller Driven Hands" setting is set to "Conforming to Controller" or "Natural."
• In Unity's XR Plug-in Management, ensure the Oculus plug-in provider is enabled for both Android and Windows.
• In PC Link, ensure that "Developer Runtime Features" are enabled.
• In the OVRHand scripts on the OVRHandPrefab objects nested under "Left/RightHandAnchor," ensure that "Show State" is set to either "Always" or "Controller In Hand or No Hand."

Do any of the things described here seem different between my setup and yours? If not, we might have to dive deeper to figure out why it behaves differently on my system versus yours. Thanks again for your patience in helping us delve into this!

Thank you very much for looking into this. I followed the listed steps exactly but still had the same outcome as before: No Hands visible. Also doublechecked the four additional points mentioned. They had all been set correctly.

I've noticed that this same problem is also being discussed in parallel in this other thread: https://communityforums.atmeta.com/t5/Unity-VR-Development/Set-up-controller-driven-hands-v65/td-p/1196675

Maybe we can consolidate our efforts in one of the two for efficiency. That way you don't have to post the same thing in different threads over and over 😉