We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.
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.
The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.
On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.
So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. 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. And always feel free to hit us up on Twitter @MxdRealityDev.
Understanding Spatial Anchors
Im currently using the the Holograms 240 project to sync an experience between multiple devices.The official microsoft dev page describes anchors a bit but Im trying to understand them in a bit more detail.
So suppose my initial Hololens device starts and it needs to create the anchors. From what I understand, it scans the room and searches for identifiable physical objects? So would it see a bottle of water, and register that physical object as the anchor? (Not sure)
Are spatial anchors determined purely by geometric characteristics? Or can anchors be identified by something such as color (Such as bright red piece of paper on the floor)
How does hololens choose what will be the spatial anchor when there are various potential anchors in the room?
Would it be possible to record a specific physical anchor, and clamp the experience to only search for that anchor? Kind of like how Vurforia uses image targets?
Im trying to streamline my AR experience and remove that waiting time of searching for anchors, creating anchors, sending anchor data across the sharing service and so on. Rather, Id just want all hololens devices in the expereince to search for a single real world reference point and not worry about learning about environment over the time. (I can guarantee a static anchor/reference point on start up for my current project)