Hello everyone.

The Mixed Reality Forums here are no longer being used or maintained.

There are a few other places we would like to direct you to for support, both from Microsoft and from the community.

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.

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, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.

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.