Recently when I was browsing on the UWP documentation, I found that the import and export of spatial anchors for collaboration experiences has been deprecated. Instead, the actual documentation is suggesting to use the SpatialEntityStore instead of the old SpatialAnchorTransferManager that I suspect Unity to use under the hood.
I wonder why this new method that you suggest is not yet used here, on a Microsoft open-sourced project. Shouldn't we try to use this new method in the Sharing part of HoloToolkit or is Unity will implements this new method instead of the actual WorldAnchorTransferBatch?
Speculation: I would suspect the reason is that most HoloLens devices in the wild are still on OS version 10.0.14393 and the SpatialEntityStore wasn't introduced until 10.0.15063 (Windows 10 Creator's update). Once HoloLens moves to 10.0.17134 (RS4), the SpatialAnchorTransferManager can finally be deprecated and the MRTK can start using the new, preferred mechanics.
but, to actually answer the proposal's question, yes, that seems like the right direction to go, once HoloLens officially moves to an OS that supports it.
But can't we start to implements this new way of sharing anchors right now, or should we wait until Windows Holographic is updated to the right version on most HoloLens devices?
Closing issues older than 180 days. If this is still an issue, please reactivate with recent information.
Most helpful comment
Speculation: I would suspect the reason is that most HoloLens devices in the wild are still on OS version 10.0.14393 and the SpatialEntityStore wasn't introduced until 10.0.15063 (Windows 10 Creator's update). Once HoloLens moves to 10.0.17134 (RS4), the SpatialAnchorTransferManager can finally be deprecated and the MRTK can start using the new, preferred mechanics.
but, to actually answer the proposal's question, yes, that seems like the right direction to go, once HoloLens officially moves to an OS that supports it.