Closed Daniel-Tamborra closed 4 years ago
I'm experiencing the same problem. Furthermore, using several watchers (one after another), Hololens 2 locate the first on correctly but then the next ones are all badly located
Hi @Daniel-Tamborra and @Merichbier. Thanks a lot for reporting this issue. We just discovered, and fixed, and bug in our Azure Spatial Anchors service, that may have been the reason behind the issue you described. Could you try your scenario again, and let us know if it's indeed fixed for you? Thanks!
Hi @RamonArguelles, Updated ASA from 2.2.0 to 2.2.1 this morning and tested. I'm happy to confirm that you did fix it
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
When creating a CloudSpatialAnchorWatcher we set the Strategy parameter on AnchorLocateStrategy to "AnyStrategy" and provide a list of Identifiers, meaning we search for multiple anchors with a single watcher.
We have multiple anchors placed and on HoloLens 1 it locates and places all of them correctly. On HoloLens 2 however it finds the nearest anchor correctly but places the rest of the anchors on position 0,0,0 in Unity Space (Where the app was launched) This is a major issue.
It does not matter whether these anchors are created on HoloLens 1 or HoloLens 2. The HoloLens 1 will locate them correctly but the HoloLens 2 (using the same settings) will only locate the nearest anchor correctly.
If we set LocateStrategy to Relationship it does not work either.