Azure Spatial Anchors are not successfully created using Hololens 2 - no anchors appearing on Azure dashboard
The tutorial I'm following is Get Started with Azure Spatial Anchors (https://learn.microsoft.com/en-ca/training/modules/azure-spatial-anchors-tutorials/3-exercise-get-started-with-azure-spatial-anchors). However, I can't create the spatial anchors successfully.
Everything on Unity was set up properly:
- The credentials match the ones on my Azure account
- All the buttons under buttonParent are set up properly.
The app was built and deployed onto HL2 successfully, but when I clicked on the create anchor button, nothing showed up here under monitoring --> metrics on MS Azure account:
I made sure that I waited for a long time and refreshed this page many times already.
There were some warnings showing up in the unity console when I was creating the build:
PS:
Unity Version: 2021.3.30f1
ASA SDK: 2.14.1
From MS website, it says the recommended unity version for HoloLens 2 development is Unity 2021.3 LTS (https://learn.microsoft.com/en-us/windows/mixed-reality/develop/unity/choosing-unity-version).
However, it also does not mention on MS website that ASA supports Unity 2021. There are only 2020 and 2019 options (https://learn.microsoft.com/en-us/azure/spatial-anchors/how-tos/setup-unity-project?tabs=xr-plugin-framework%2Cunity-2020%2Cunity-package-mixed-reality-feature-tool%2CExtraConfigurationsHoloLens).
Can you confirm that ASA supports unity2021.3 LTS?
Thank you~
2 answers
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more