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.
WorldAnchorTransferBatch.ExportAsync returns empty blob
WorldAnchorTransferBatch.ExportAsync seems to return empty binary blob after completion if around 50% of the times. If I try to run it again, it usually works (might take few tries). There does not seem to be any correlation between ExportAsync failing and initial conditions.
This issue seem to be known before. In the Holograms 240 tutorial that was released over a year ago, they have a check for a minimum result size. This is the piece of code that checks for the file size in the tutorial:
///
const uint minTrustworthySerializedAnchorDataSize = 100000;
...
public void ExportComplete(SerializationCompletionReason status)
{
if (status == SerializationCompletionReason.Succeeded && exportingAnchorBytes.Count > minTrustworthySerializedAnchorDataSize)
...
Is there a known fix/workaround? Or does anyone know exact reason why this happens?
Best Answer
-
Optionsstepan_stulov ✭✭✭
Hey, @NikT
As far as I remember, this issue is so known that there is a variable a'la SerializationAttemptCount somewhere in the HoloToolkit that's set to 3 by default. You can do the same and retry multiple times. It has even been confirmed by a Microsoft engineer somewhere on the forums that transfer batches are not very reliable at the moment.
Building the future of holographic navigation. We're hiring.
6
Answers
Hmm thats interesting i also have problems with the export of worldanchors, sometimes it works sometimes it doesnt. But i never really dived into why this is happening^^
Hey, @NikT
As far as I remember, this issue is so known that there is a variable a'la SerializationAttemptCount somewhere in the HoloToolkit that's set to 3 by default. You can do the same and retry multiple times. It has even been confirmed by a Microsoft engineer somewhere on the forums that transfer batches are not very reliable at the moment.
Building the future of holographic navigation. We're hiring.