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.
Questions about world anchor sharing.
I'm having troubles sharing world anchor between multiple devices:
1) When I try to serialize/deserialize large anchor blob (about 25 mb), I receive error: world lock deserialization failed hololens. The only way to prevent it, is to delete the space data from settings, but doing this every time is too much. Is there a way to prevent this error?
2) What affects the anchor size? I thought it depends only on current space, more hololens knows -> more anchor byte array
3) I mentioned, that 100% accuracy in sharing is reached by having anchor size more than 18 mb for large room, or, when more than 80% of the room has mesh data. But this amount is not generated immediately. Is it possible to run SurfaceObserver, scan the room and use generated data.? Is it possible to save SurfaceMeshes directly to device memory?
4) Is it possible to force anchor locating process? So the isLocated became true?