Hello everyone.

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.

Space grows when deserializing WorldAnchorTransferBatch based on a bigger space but...

stepan_stulovstepan_stulov ✭✭✭
edited December 2017 in Questions And Answers

Hello everyone.

Full question title should have been:

Space grows when deserializing WorldAnchorTransferBatch based on a bigger space but without learning more of the environment.

I have noticed an interesting and somewhat unexpected behaviour that I would like to be commented on or clarified. This is all based on Unity.

Here is a step-by-step reproduction of what I did:

  1. Clear the current space in the settings.
  2. Make sure to walk around enough so that the newly created space grows to a bigger size. In my case it was some 45mb.
  3. In an app create some good number of objects, say 200, objects with world anchors, construct a WorldAnchorTransferBatch of them, serialize it and save it to disk.
  4. No remove the space in the settings again and do not walk around much but make sure your space is somewhat smaller. In my case it was 19mb.
  5. Now launch a app that loads that previous WorldAnchorTransferBatch, deserializes it and creates a game object for each anchor in it. Anchors work and objects snap in place.
  6. Now check the size of the space in settings. It's back to the bigger size that that WorldAnchorTrnasferBatch was based on despite the fact that your head absolutely did no travel around enough to provide the additional extra size of the space.

This leads me to a couple of speculations:

  1. When unpacking a WorldAnchorTransferBatch the system recognizes that the smaller and the bigger are two versions of the same space and simply merges the two enriching the smaller one. This conclusions seems more likely to me.
  2. The space doesn't just contain the spatial data but also the anchors in some form. This conclusion seems less likely to me due to the very temporary nature of anchors. Space can't contain every anchor.

I welcome everybody to share their objections, ideas or plain better conclusions to why the space grows upon deserializing a WorldAnchorTransferBatch without really learning more about the environment.

Cheers

Building the future of holographic navigation. We're hiring.

Answers

  • Alright, so let me ask the next questions:

    (1) Is it possible to walk the space on one and define the room, freeze it to a file (or snag the file that was created) and save that to a server so that every future execution or headsets joining the environment can begin their experience with the same room definition each time? If so, where would I find that file?

    (2) Is this observation valid for both the Hololens and the Full Immersion Headset?

Sign In or Register to comment.