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.
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.