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.

Motion Controller thumbstick deadzone

Using Unity 2017.2.0f3 / Build 16299, retrieving the value from InteractionManager > InteractionSourceUpdated >InteractionSourceUpdatedEventArgs (args.state.thumbstickPosition), the center/neutral Vector2.x value goes as high as 0.19+ and sometimes even 0.20+. It's only happening on my left-controller thumbstick and the usual values for the right stick and vector components deadzone is usually less than 0.09.

Anyone else experiencing a high deadzone range? or is there a re-center workaround for the thumbsticks?


  • yep I see the same thing here

  • I guess it's within manufacturing tolerance -- the Cliff House treats the value within the deadzone. App Developers would need to consider the value range (I noticed this issue while running Dark Legion with "smooth" movement)

Sign In or Register to comment.