ikto-art
commented
1 year ago I also tried ignoring the validation checks in SpatialAnchorManager.cs and got this error from ASA:
System.InvalidOperationException: Azure Spatial Anchors requires xrConvertWin32PerformanceCounterToTimeKHR, xrTryGetPerceptionAnchorFromSpatialAnchorMSFT, xrCreateSpatialAnchorFromPerceptionAnchorMSFT, xrCreateSpatialAnchorMSFT, and xrReadSpatialAnchorNeighborhoodDataMSFT extensions avaialble.
I forgot to write earlier that the first time I ran the UWP build it seemed to not be able to find an available XR runtime or connect to the HoloLens 2 so I added one manually that pointed to Microsoft.Holographic.AppRemoting.OpenXr.dll and then it worked.
Now I just tried to install the Microsoft app 'OpenXR for Windows Mixed Reality' and set it as the available runtime but in the log there were errors of XR_ERROR_FORM_FACTOR_UNAVAILABLE then it apparently automatically switched to the remoting runtime that still lacks the extensions (but the Microsoft app runtime had the XR_MSFT_perception_anchor_interop extension).
dfields-msft
Varnauld
darax
Description
I can't use the SpatialAnchorManager script in Unity when I try to use it in a build, after establishing a connection to a HoloLens 2 with OpenXR remoting.
Steps to reproduce the issue
Basic project which uses the Mixed Reality OpenXR 2.8.1 remoting runtime and MRTK 2.8.2 on Unity 2020.3.41 with UWP build. When running built player and calling SpatialAnchorManager.CreateSessionAsync() after the remoting session is established it says SpatialPerception capability not enabled (of course the package manifest has the SpatialPerception authorization).
Development information (please complete the following information)
AR Device information (please complete the following information):
Additional context
In the UWP build, a script connects to the HoloLens 2 with AppRemoting.Connect() then when connected waits 3 seconds for OpenXR sessions status to go to 'Focused' and then tries to create and start a session with SpatialAnchorManager.CreateSessionAsync().
In the log I have the following report before the call to
Windows.Perception.Spatial.SpatialAnchorExporter.RequestAccessAsync():I see this extension that might be needed that's not supported: XR_MSFT_spatial_anchor_export_preview But the 2.8.1 remoting library changelog seems to imply that Azure Spatial Anchors are working with Remoting.