Hello everyone.

We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.

The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.

The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.

On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.

So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality. If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers. And always feel free to hit us up on Twitter @MxdRealityDev.

Understanding MixedRealityTeleport script of MixedRealityCameraParent

I'm testing motion controllers tracking by retrieving their (local) positions using sourcePose.TryGetPosition.

All seems to be fine except when I'm teleporting using MixedRealityTeleport script of MixedRealityCameraParent (default Holotoolkit settings). In this case, tracked positions are shifted by the teleport jump (same thing for rotations).

So, I've edited the script to understand a bit more: teleportation changes the MixedRealityCameraParent's position rather than the position of the camera... and so tracked positions are no more relative to the MixedRealityCamera itself.

Why this choice ? Is there a good way to correct this so that the retrieved positions and rotations (TryGetXXX) correspond to the actual controllers positions and rotations ?

Tagged:

Answers

  • The position and rotation from TryGetposition is determined by motion controllers' physical locations. In order to represent the relationship between the headset and motioncontrollers, we put them under a same parent gameobject: MixedRealityCameraParent. You can seem the headset as your eyes, motion controllers as your two hands. When you teleport, eyes and hands should move together, so we need a parent object as your body.
    If I misunderstood, please tell me.

Sign In or Register to comment.