Azure Spatial Anchoring Accuracy When Using Holographic Remoting

[Kiwithepaladin]

Description

Hi, I'm using two HoloLens devices with Netcode for GameObjects as my networking solution. What I am trying to achieve is that two HoloLens will have a shared anchoring point thus I can share the display data (say a cube) on the exact same spot in real world for two different devices.

I utilize Netcode for GameObjects by unity to keep the identifier of the anchor I have created so when a new user connects to the system, it will start looking for it by using an ASA watcher which gets a by identifier criteria.

Problem rises whenever I retrieve the ASA and said anchor has about 1 meter offset from the original source.

Steps to reproduce the issue

HoloLens 1:

• Go to a room / place the HoloLens in a different room
• Starts Holographic remoting
• Connects to the system
• Scans the room up to a point in which ReadyForCreate gives me a value of 15 or greater.
• Creates an anchor and store his Identifier as a Netcode NetworkVariable so it can be shared across multiple users.
• Locate an anchor and spawn a 3d Object so I can identify its position in the real world

HoloLens 2:

• Starts Holographic remoting
• Connects to the system
• Checks if the NetworkVariable has a value, if it doesn't, a new anchor will be created (we never get to this part which is good), if it does, using said NetworkVariable value (which keeps the identifier) we add it to the criteria so that the watcher will look for.
• Go to the same room in which the anchor was created.
• Anchor Located and spawn a 3d Object so I can identify its position in the real world

Expected behavior

I've used ASA about 6 months ago as an app that runs on the HoloLens itself, I stopped using ASA for a while, and since I read that Holographic Remoting is now being supported in the latest patch notes from release 2.14.1, I gave it another try.

In my last usage of ASA (as said 6 months ago) I ran it on the HoloLens itself, and the margin of error on the 3d Object I was creating on two different HoloLens was significantly smaller.

I expect that the margin of error (how far the object is from where it was originally created) will be smaller.

Development information:

• OS: Windows
• Development Platform\Version: Unity 2021.3.25f1
• Azure Spatial Anchors SDK version: 2.14.1

AR Device information:

Device: HoloLens 2 utilizing holographic remoting

Additional context

I'm still experimenting and testing what might cause this offset (e.g: it purely from Holographic Remote or if it there is a step I have missed) l will update this Bug Report whenever I find new things.

[lagenuina]

Hi, I am not able to use Holographic Remoting with Azure Spatial Anchor. Have you ever run into this error?

DllNotFoundException: AzureSpatialAnchors assembly: type: member:(null) Microsoft.Azure.SpatialAnchors.AnchorLocateCriteria..ctor () (at Library/PackageCache/com.microsoft.azure.spatial-anchors-sdk.windows@c59f29caea85/Runtime/AzureSpatialAnchorsBridge_Windows.cs:2199) AnchorModuleScript.Start () (at Assets/MRTK.Tutorials.AzureSpatialAnchors/Scripts/AnchorModuleScript.cs:40)

[hyungilkim]

Hi, I am not able to use Holographic Remoting with Azure Spatial Anchor. Have you ever run into this error?

DllNotFoundException: AzureSpatialAnchors assembly: type: member:(null) Microsoft.Azure.SpatialAnchors.AnchorLocateCriteria..ctor () (at Library/PackageCache/com.microsoft.azure.spatial-anchors-sdk.windows@c59f29caea85/Runtime/AzureSpatialAnchorsBridge_Windows.cs:2199) AnchorModuleScript.Start () (at Assets/MRTK.Tutorials.AzureSpatialAnchors/Scripts/AnchorModuleScript.cs:40)

I ran into same error as @lagenuina, too. Is there any solution for this?