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.

Tips for asking for help

edited September 2017 in Q&A and Discussions

A lot of issues that are getting filed right now are due to the wide range of development environment variables and versions of the various tools we use.

To help facilitate the quickest response to your questions, it would be helpful if you could provide the following info when submitting an issue:

  • Unity development or C++/CX/DirectX
  • Unity Version
  • Visual Studio Version
  • MixedRealityToolkit Version
  • Windows Build Number
  • Description of what you are trying to do (What are you expecting to happen)
  • Description of what is actually happening
  • Error messages/Screenshots/Etc
  • Input Modes (Xbox Controller, Motion Controllers, Etc)

For convenience, it may make sense to even place this in your for signatures.
For example, my current dev environment is:
VS 2017 v5.3.3, Unity 2017.1.0p5, MRTK 2017.1.1, W10 16281
The more we all do this, the easier our lives will be.

Thanks to @james_ashley and James Doyle for the suggestions

Sign In or Register to comment.