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.
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.
DaTruAndi ✭✭
Reactions
-
Re: VS2017/U5.6 Crash - WinRTScriptingObjectWrapper::InternalAddRef Reference Count cannot be zero
I have the same problem with Visual Studio 2015. For @Jimbohalo10 . This is not in the domain of Visual Studio, this happens internally in Unity! @neerajwadhwa : WorldAnchorManager together with Unit… (View Post)-1 -
Re: VS2017/U5.6 Crash - WinRTScriptingObjectWrapper::InternalAddRef Reference Count cannot be zero
@Jimbohalo10 I do not understand your response. This is not a repro for 5.4 and 5.5. This is about a problem in Unity 5.6 and 2017 b1 - again I was not talking about 5.4 or 5.5. It works on 5.4 and 5… (View Post)2