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.
UNET Master Build not working
I have a project that connects multiple hololens devices with UNET. The release build works fine. But building on master causes connection issues. I am using network discovery and networkmanager HLAPI components and I was able to pinpoint the issue to the fact that when ever networkmanager and discovery are started together, it causes abnormalities (I'm not able to connect to the server). When I introduce a delay between the Networkmanager.singleton.StartHost() and _networkDiscovery.StartAsServer() things work "better". Any ideas to why this is happening ?
Let me know if more info should be added to explain this better.