Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
TAIC_Dev's avatar
TAIC_Dev
Explorer
5 years ago
Solved

Controller Tracking not working when OVRCameraRig is moved

Hi folks,
so I am working on an application for the Quest 2. We use the standard OVR prefabs as a base and have elaborated on their functionality. Until now everything is working fine but today I wanted to the functionality to move the user around by lerping the users position towards another object - basically making the user follow the object. 
Here the issue arose - when I move the user around, the hands will not update their position anymore. I don't really understand why but I guess the OVRManager/CameraRig stopps updating the hand positions as soon as the user moves around. 
So is there a way to fix this issue or can someone tell me what is causing this so I can maybe come up with a solution or workaround?
Help will be greatly appreciated 🙂 

  • Anonymous's avatar
    Anonymous
    5 years ago

    You probably have the hand prefabs at the root of the scene with "Update Root Pose" checked. Instead the hands should be in the camera rig prefab, as children of the *HandAnchor transforms, with the "Update Root Pose" checkbox unchecked.

     

    Also, the "Pointer Pose Root" field in OVRHand should be set to the TrackSpace transform.

2 Replies

Replies have been turned off for this discussion
  • Anonymous's avatar
    Anonymous

    You probably have the hand prefabs at the root of the scene with "Update Root Pose" checked. Instead the hands should be in the camera rig prefab, as children of the *HandAnchor transforms, with the "Update Root Pose" checkbox unchecked.

     

    Also, the "Pointer Pose Root" field in OVRHand should be set to the TrackSpace transform.

    • TAIC_Dev's avatar
      TAIC_Dev
      Explorer

      Thanks for your reply!
      I moved the hand prefabs to be children of the HandAnchor transforms and set the TrackingSpace in the Pointer Pose Root field as you said and that fixed the issue.
      Thanks a lot 🙂