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.
Change to Mixed Reality Toolkit Dev_Unity_2017.2 branch today
Today @stephenhodgson and I are going to be merging the Main branch of the HTK into the Dev_Unity_2017.2 branch. There is a pretty wide gap of things that have gone into the Main Branch that have not gone into the Dev branch, and we need to close that gap to move forward. This may cause breakage in the Dev branch. If you need a stable version of the Dev_Unity_2017.2 branch, you can get it here - https://github.com/Microsoft/MixedRealityToolkit-Unity/releases - marked as 2017.2 Pre-release.
What will be super helpful is for you guys to maybe make copies of your projects that use the Dev_Unity_2017.2 branch, or even Master, and test out all the parts of your projects using it. Let us know where it's broken, what pain points there were to upgrading, etc. File the issues on Github so we can track them. If you have any questions, feel free to reach out to me.