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.
What are the differences in the spectator view documentation and the current version of the code?
It appears the spectator view documentation and the available code are out of sync. I was wondering if there is some place that has documentation that is more applicable to the code. I'm running into a few problems in getting spectator view working and I think the solutions might be in such documentation (if it exists).
I'm currently trying to follow the instructions available here:
https://developer.microsoft.com/en-us/windows/mixed-reality/spectator_view
In the instructions is the following:
Spectator View IP should be the IP of your HoloLens attached to your spectator view rig.
Sharing Service IP should be the IP of the PC running the HoloToolkit SharingService.
I don't see the sittings mentioned, and the available options to me are different than what is listed in the documentation.
Additionally I can see that even if the sharing service isn't running that there is differences in behaviour in the application that indicate that instances of the application on different devices are communicating with each other. (Is the sharing service even still necessary?).
For me the sample project when run on the Spectator view PC renders a disc over the video stream from the camera. The disc is always in the same position and orientation.
From the individual hololens devices if the spectator view PC isn't running the project present me with a menu to join or start a session. The moment the project starts running on the spectator view PC this menu goes away. I can see the gaze cursor, but nothing else. The disc never renders.
If I select the option to create a session from a hololens (without the spectator view pc running the project)I can see the disc. If I start the application on another hololens it shows the first hololens as hosting an available session. If I join that session on the second hololens I only see the gaze cursor but it never renders any part of the scene.
The code and the behaviour are much different than what is described in the above mentioned documentation. Does any one know what all the variances are?
Answers
I think I just found **part **of the answer to my own question. Within the last month the Spectator View code was updated to no longer make use of the sharing service. Instead it us using networking services that are part of Unity now. The page I referred to above contains the documentation for a previous version of the code.
The ReadMe.md in the code repository has comments that are consistent with the code that I'm looking at, though it isn't sufficient to get the system behaving as one would expect. The Compositor is rendering on top of the video stream but it appears no other HoloLens is receiving information on the shared anchor which is necessary to get the scenes synced up.
https://github.com/Microsoft/HoloLensCompanionKit/blob/master/SpectatorView/LegacyDocs/SharingService/Samples/README.md