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.

What is the projected distance of the screen in Windows Mixed Reality Headsets?

Hello everyone,
I am interested in the Hardware specifications of the Windows Mixed Reality Platform immersive HMDs. Especially at which distance the screen is perceived considering only accomodation and not stereoscopy?
In HoloLens the accomodation distance for objects displayed is 2m (according to this paper: http://onlinelibrary.wiley.com/wol1/doi/10.1002/sdtp.11586/abstract).
Is there any information about the accomodation distance in the fully-immersive HMDs?
Is it the same for all WMR immersive HMDs (of all vendors)?
Are there any papers, guidelines or patents on this subject?
Thank you in advance! :)


  • After searching some more, I found this:
    "In general, the focal distances to these displays are between 1.25m-2.5m. When in doubt, avoid rendering objects of interest too near to users and instead try to keep most content 1m or farther away" from https://developer.microsoft.com/en-us/windows/mixed-reality/comfort
    Unfortunately, this only answers the question partially. Now, I know that the distance of the focal plane is somewhere between 1.25 and 2.5m; however it would be really interesting to know if there is any way to get the distance of this focal plane (which is defined by the optical set-up of the HMD) for a specific HMD. Alternatively, it would be even better to be able to get it dynamically from code during run-time of the app.
    If you are asking yourself "why the **** does this matter?" - I am doing research :)

Sign In or Register to comment.