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.
Spaces getting too big results in failed WorldAnchorTransferBatch.ExportSync
seb
✭
So apparently one of my "Spaces" was getting big, namely 300 MB. Not sure how this works internally but it seems to accumulate over time.
I was trying to send a world anchor to other Hololenses and the WorldAnchorTransferBatch.ExportSync failed with "Unknown Error". First off, that error message is not very helpful at all and should be fixed in the SDK. Secondly, clearing the space (Settings->Spaces) made everything work again. Blazing fast I might add.
However, it is a mild inconvenience that the users need to go into the system settings every now and then to clear this.
Does anyone know if we programmatically can clear spaces?
Best Answer
-
stepan_stulov
✭✭✭
Hey, @seb
It's not possible to programmatically clear spaces, there is no API for that. Also the fact that spaces are on the system/OS level and not on the app level (arguably) indicates that one app having power to mess with the OS level would be a bad idea.
World anchor transfer batch exporting is known (and confirmed somewhere on the forums by a Microsoft employee) to be unreliable. Sometimes it may not export, and then another retry will work on the same batch. There is something like a "attempt count" variable somewhere in HoloToolkit set to 3. That's how many times they try to export the batch before it's "officially" failed.
Spaces tend to grow the more HoloLens is used inside of the same environment. Perhaps it stores new knowledge of the environmental changes accumulatively and doesn't clean up old stuff. That's a pure speculation though. World anchor transfer batch also seems to simply have the entire space packed into it.
Hope this helps.
Building the future of holographic navigation. We're hiring.
5
Answers
Hey, @seb
It's not possible to programmatically clear spaces, there is no API for that. Also the fact that spaces are on the system/OS level and not on the app level (arguably) indicates that one app having power to mess with the OS level would be a bad idea.
World anchor transfer batch exporting is known (and confirmed somewhere on the forums by a Microsoft employee) to be unreliable. Sometimes it may not export, and then another retry will work on the same batch. There is something like a "attempt count" variable somewhere in HoloToolkit set to 3. That's how many times they try to export the batch before it's "officially" failed.
Spaces tend to grow the more HoloLens is used inside of the same environment. Perhaps it stores new knowledge of the environmental changes accumulatively and doesn't clean up old stuff. That's a pure speculation though. World anchor transfer batch also seems to simply have the entire space packed into it.
Hope this helps.
Building the future of holographic navigation. We're hiring.
Here:
https://forums.hololens.com/discussion/1171/worldanchortransferbatch-failures
Building the future of holographic navigation. We're hiring.
This is not quite what was happening to me though. I think the Hololens should in fact have an overlay where the user is asked if Spaces can be cleared. My error doesn't even give a hint on WHAT the issue is. i.e. "Unknown Error". At the least the SDK should provide information on why it failed.
Thanks for the information though.