Deserialization succeeds but 0 anchors in batch

So I've been transferring a serialized anchor using TCP. I have been debugging this issue and I know the received bytes are exactly the same as on the sender.

However, when I import the data and the subsequent OnDeseralizationComplete handler is called it says it has succeeded BUT looking at the deserialized batch, it contains 0 anchors.

It worked once I think but that is about it. How should I proceed with debugging? I can't think of anything else than this being a bug somewhere in Unity? How can it succeed but still contain 0 anchors?

I'm using 2017.1.1.f1

 

Thanks for you answer @unity_andrewc . Let me explain a bit more:

The API call I'm doing is:

Code (CSharp):

1. WorldAnchorTransferBatch.ImportAsync(data, OnDeserializationComplete);

According to documentation that calls the OnDeserializationComplete when it finishes. My method for this looks like so:

Code (CSharp):

1. private static void OnDeserializationComplete(SerializationCompletionReason completionreason,
2.             WorldAnchorTransferBatch deserializedtransferbatch)
3.         {
4.             if (completionreason != SerializationCompletionReason.Succeeded)
5.             {
6.                 // Failed
7.                 if (_retryCount > 0)
8.                 {
9.                     _retryCount--;
10.                     WorldAnchorTransferBatch.ImportAsync(_exportedDataBuf, OnDeserializationComplete);
11.                 }
12.             }
13.  
14.             print("[Client]: Deserialization completed with: " + completionreason + " Number of anchors: " + deserializedtransferbatch.anchorCount);
15.             if (deserializedtransferbatch.anchorCount > 0)
16.             {
17.                 AnchorImportedHandler(deserializedtransferbatch);
18.                 HololensClient.Instance.SendToServer(TMsgType.Error, new TMessage() { Description = completionreason + ": " + deserializedtransferbatch.anchorCount});
19.             }
20.         }

The print call here gives me this line in console:
[Client]: Deserialization completed with: Succeeded Number of anchors: 0

I cannot understand how the deserialization can succeed if there are no anchors included. I should say that the sender lists the batch with 1 anchor correctly berfore sending it using TCP. I have even printed out the last 200 bytes from the sender and the receiver and they match exactly. Any clues?

This is all in the same app and should happen in runtime. I'm using UNET for messaging and a custom TCP client/server to do the hauling. Note that this is before actually placing/locking anything. In order to do that I need a reference to the actual anchor

Testing is done on two Hololenses. No remoting.

Edit: how do I format code?

 

That is not really how it works though. The spatial information is constantly adding up in the internals of the Hololens. Thus the more you actually use it, i.e. scan the room, the bigger the achors tend to get. It is never a static size if that is what you mean? More anchors would probably size it up quite a bit, especially if the placement is not in the same room but in a completely different place. But even using only one anchor I've seen anything from 300k to 12 MB. The "trick" is to reset the space, which can be done in Hololens settings. I've verified this with Hololens Forums.

Should I still try this or should I file a bug? Not sure if that is actually going to add anything.

 

I doubt it is. First I'm getting a successful export and then a successful import (but no anchors). Important to note is that the export does indeed list one anchor with the correct id and everything (and the data seems to be the same on both ends comparing binaries)

 

OK will do

 

OK @unity_andrewc I filed the report on friday. If you have any questions about the implementation feel free to reach out to me.