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.

HoloLens - distance tracking accuracy problem

edited March 2018 in Discussion


We are testing our app on the HoloLens and found a huge issue with the distance tracking. The error margin is 25%-40% (for every 10 m walked, HoloLens will be off by 2.5-4M) under the ideal light conditions. The device failed to track the rotation accurately too - a 180d turn will cause the device to be off by nearly 10d.

For comparison, iPhone 6s with a single camera had the error margin of 2% during the same test and virtually no issues with tracking rotation.

The same app, running on the same device used to be a lot more stable and accurate just 6 months ago. Did the recent HoloLens update introduce these problems? Also, what is the remedy? Spacial anchoring has no effect.


  • I get better results with rotation, in my case it seems to be rather close on the money ... as far as distance tracking, don't know.

    Though in a smaller space, say 16ft X 25 ft, the measurements seem pretty good, not getting errors like you mention. There is a sample program that let's you measure from point to point that, back then when last used, was easily within 5% margin of error, and at times seemed nearly exact (this for room measurements, but not for small items).

    A recent update seemed to cause slowdown in processing, but once I updated everything to latest, it seems to speed up some, in particular updating UWP to the latest 6 version.

    Can you be more precise in details about what you are rotating that isn't tracked well? Are you rotating an object and it's isn't rotated the correct amount? Or are you using visual feedback to determine the amount of rotation, say by using some gesture to rotate the object?

Sign In or Register to comment.