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.
Spectator View setup - Coding the World Anchor transfers
I am reading through the Unity documentation on app development for the HoloLens. I noticed a page called "Anchor Sharing," where you need to define a function for exporting an anchor, a listener for the status received on exporting the anchor, and on the event where the data of the anchor becomes available.
Suppose that I want to add Spectator View to a simple app of my own with a red cube as my only object (in turn is an anchor). I am able to add in the assets from the Mixed Reality Companion Kit downloaded from the GitHub repo, but do I still need to program a script to export a world anchor in order for a secondary HoloLens to see the cube locked in place and looking at it from a different viewpoint than the Spectator View rig sees it?
It's a bit confusing; the README file for the Spectator View sample the toolkit provides doesn't really say to program an anchor export script explicitly and specify which objects are to be exported to the other HoloLens in order for the user to see them as the real thing but from a different viewpoint.