The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
How does 'space' spatial information influence in-app spatial meshes
In which way, if any, does the saved “space” spatial information you can access through the Settings/System/Spaces Menu have an influence on the spatial mapping experience in your apps?
When experimenting with the SpatialMapping prefab in the HoloToolkit, I find that the current space is not changed through manipulation of a SpatialMappingManager in the app (clearing the observer, adding a different SpatialMappingSource, clearing that source etc.).
Apparently, the only way to get rid of a space is to delete it from the Settings menu.
But does the space on the other hand have an influence on my app’s experience?
Is it still updated even though I stopped the SpatialMappingObserver?
Do my holograms refer to the space in any way?
Especially, when I attach world anchors in an app that uses a pre-scanned spatial mesh with the observer stopped, will the world anchors still respond to any changes in the underlying space’s spatial information (e.g. a new piece of furniture etc.)?
Thanks a bunch for any help.
Best Answer
-
Options
stepan_stulov
✭✭✭
On spaces.
Spaces are system-global, it would be a mess if one app could adjust it to its needs and thus influence the others. HoloLens tries to keep current space as updated as possible "no matter what". This process, unless there are some hacky ways, is unstoppable. What your app gets at a certain rate and certain resolution is the most recent snapshot of the spatial mesh, possibly processes/smoothened. However you modify it, it is just that - modifying the snapshot. You run your raycasts, visualize the mesh and do whatever else but you always do it against the most recent snapshot and not the actual space you can see in the settings.
On anchors.
Anchors, as far as I know, do not fully (if at all) rely on the spatial understanding but on tracking. Stabilizing the anchors also runs against the real-time space / point cloud. You cannot tell anchors to be anchored to your local spacial snapshot. The misunderstanding of what the anchors are based on comes from the fact that one (conventionally) first needs to find a raycast point on the spatial mesh and then attach an anchor. While the anchor itself is then not really based on that same spatial mesh.
You cannot truly substitute HoloLens's spatial understanding with an adjusted/pre-modeled/modified scan in relation to its fundamental processes. The feed is one way.
Building the future of holographic navigation. We're hiring.
7
Answers
@Fiedel
On spaces.
Spaces are system-global, it would be a mess if one app could adjust it to its needs and thus influence the others. HoloLens tries to keep current space as updated as possible "no matter what". This process, unless there are some hacky ways, is unstoppable. What your app gets at a certain rate and certain resolution is the most recent snapshot of the spatial mesh, possibly processes/smoothened. However you modify it, it is just that - modifying the snapshot. You run your raycasts, visualize the mesh and do whatever else but you always do it against the most recent snapshot and not the actual space you can see in the settings.
On anchors.
Anchors, as far as I know, do not fully (if at all) rely on the spatial understanding but on tracking. Stabilizing the anchors also runs against the real-time space / point cloud. You cannot tell anchors to be anchored to your local spacial snapshot. The misunderstanding of what the anchors are based on comes from the fact that one (conventionally) first needs to find a raycast point on the spatial mesh and then attach an anchor. While the anchor itself is then not really based on that same spatial mesh.
You cannot truly substitute HoloLens's spatial understanding with an adjusted/pre-modeled/modified scan in relation to its fundamental processes. The feed is one way.
Building the future of holographic navigation. We're hiring.
Hello Stepan,
Thank you very much for your comprehensible explanation. This helps me a lot!