Hello everyone.

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.
Options

Co-located anchors via sharing (export/import) are way off.

Is this the best the tech can do? Or did I program something wrong.

I'm using the example here https://docs.microsoft.com/en-us/windows/mixed-reality/shared-spatial-anchors-in-directx#example-send-anchor-data-using-a-windowsnetworkingstreamsocket

Anchors export and import without error, but the content is off by sometimes as much as an entire foot. Is this just the limitation of anchors? Or am I doing something wrong? I was hoping my anchored scale model hologram (0.5 meters) would appear in the exact same position on both devices (at least within the width of the model itself). Kind of disappointing...

Answers

  • Options

    I have heard this too. That is one of the reasons why we don't have a shared Holographic experience in our application because it would no where near be accurate enough.

  • Options

    I find it works decent enough if you position holo content in empty space and not near walls or on tables. Then it's close enough. Accuracy seems to increase with subsequent co-locations.

Sign In or Register to comment.