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.

Attn: HoloLens Documentation Tech Writers - Voice Design Article Minor Misprint?

Minor feedback thing. Don't see where you can comment/feedback on the beta HoloLens documentation, but noticed that it seemed like a misprint in the "Designing holograms" > "Voice Design" article.

It abruptly switches to non-voice, seeming off-topic, visual related design tips about 6 bullets into the Voice section, I think by accident.

"Scan a substantial portion of the environment before placing holograms or consuming surfaces from spatial mapping. Scanning builds the map used by the tracker. (It also generates surfaces provided by spatial mapping.)
Allow tracking cameras to see as much of the environment as possible. Do not, for example, have the user stand very near, and directly face, a blank wall or cover the tracking cameras with hands or hats.
Operate the device in an environment with sufficient visual complexity. Visual tracking works better when the environment contains trackable features.

Operate the device in an environment with adequate lighting. Visual tracking works better when trackable features are visible."

Thanks for the great documentation and content, much appreciated.

Comments

  • Thanks for flagging this -- we're looking into it now.

    And btw, for the time being, this (the forums) is the best place to give us feedback on the documentation.

Sign In or Register to comment.