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