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.
Hololens Spatial Anchor Sizes
I'm working on a script to share anchors between Hololenses and have been having some trouble with the sizes of the anchors. It varies but I've measured the anchors to be around 160mb . The most I can get out of the Low-Level API TransportNetwork that Unity uses is around 1000 bytes per transfer. With transferbatches approaching 0.2 GB, the time to transfer an anchor is more easily measured in minutes or hours rather than seconds. In fact, I've yet to successfully transfer a sign anchor because of this. Am I mismeasuring the anchor somehow? If not, what determines the transferbatch's size? Any advice on how to approach this issue?