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.
Is this the proper workflow for Holograms_240 (SharingService)?
Greetings,
I am having difficulty connecting two machines using the SharingService as outlined in HoloGrams_240.
I've created the project as specified by the page; I've then built it twice. Once on the Server machine with "localhost" (and alternatively, the host machine's own IP address), and once on the Client machine using the IP address of the Server machine for the "Server Address" field on the Sharing prefab. On this build, I've also tried toggling the "Client Role" to Secondary (as well as Primary and Unknown).
I've also tried using the Sharing.unity example from the HoloToolkit. Regardless of Project, when running the Build on the Secondary machine, I do not see a trace of a successful join in the SharingService of the Primary machine.
I've tried running the Project Build on the Server machine and Client machine with various combinations of two HoloLens devices or two Emulators. Nothing seems to do the trick. I've also tried simply running Preview mode in Unity.
Pinging the Host machine from the Client machine is successful; the ports are matching on both ends.
My understanding of machine networking is limited. Can anyone confirm my approach is correct, or better yet suggest some first steps to debugging this issue?
Thank you for your support,
Sally
Best Answers
-
OptionsPatrick mod
okay, cool. Then that shouldn't be a problem. The actual app is running on the HoloLens you deployed to.
A couple of things to check:
1. Sometimes the IP Address to use isn't obvious. When you run the sharing service it will give you a list of possible IPs to use.
something like:Local IP addresses are:
127.0.0.1
192.168.1.1
169.254.80.80(I made up the IP addresses above) In my case I have three and have learned to pick the one in the middle. That might not be the same for you.
In the prefab in Unity make sure your Server Port is set to 20602.
The Client Role should be primary on all systems.
- The Server Address should be the same on all systems.
One thing you can do, is press play in the Unity Editor, and you should see the connection get made if everything is setup properly. If you do this, however, it's vital to restart the sharing service before actually trying the demo.
===
This post provided as-is with no warranties and confers no rights. Using information provided is done at own risk.(Daddy, what does 'now formatting drive C:' mean?)
6 -
OptionsPatrick mod
BTW, the shared experience lab could be done with a single PC running the sharing service and two HoloLens devices. The PC would need to deploy from Visual Studio to each of the HoloLens devices. When we were actively working on the lab we would often set our build target to 'device' instead of 'remote machine' and swap which HoloLens device we had connected to the USB on the PC we were working on.
===
This post provided as-is with no warranties and confers no rights. Using information provided is done at own risk.(Daddy, what does 'now formatting drive C:' mean?)
5
Answers
Hi Sally.
Only one PC should be running the sharing service. The IP Address of the machine running the sharing service should be put in the Server Address field of the prefab on all PCs building the experience.
===
This post provided as-is with no warranties and confers no rights. Using information provided is done at own risk.
(Daddy, what does 'now formatting drive C:' mean?)
Hey Patrick,
Thank you for the comment. This is the case, although the single machine running the Sharing Service is also running a game build, acting as both the Server and a Client.
Could this be the issue? Is it expected that a third machine should be running the Service independent of the two Player machines?
Thank you for your support.
Best,
Sally
What do you mean by running a game build?
===
This post provided as-is with no warranties and confers no rights. Using information provided is done at own risk.
(Daddy, what does 'now formatting drive C:' mean?)
By "running a game build", I mean that I have done the following:
Thank you!
okay, cool. Then that shouldn't be a problem. The actual app is running on the HoloLens you deployed to.
A couple of things to check:
1. Sometimes the IP Address to use isn't obvious. When you run the sharing service it will give you a list of possible IPs to use.
something like:
Local IP addresses are:
127.0.0.1
192.168.1.1
169.254.80.80
(I made up the IP addresses above) In my case I have three and have learned to pick the one in the middle. That might not be the same for you.
In the prefab in Unity make sure your Server Port is set to 20602.
The Client Role should be primary on all systems.
One thing you can do, is press play in the Unity Editor, and you should see the connection get made if everything is setup properly. If you do this, however, it's vital to restart the sharing service before actually trying the demo.
===
This post provided as-is with no warranties and confers no rights. Using information provided is done at own risk.
(Daddy, what does 'now formatting drive C:' mean?)
BTW, the shared experience lab could be done with a single PC running the sharing service and two HoloLens devices. The PC would need to deploy from Visual Studio to each of the HoloLens devices. When we were actively working on the lab we would often set our build target to 'device' instead of 'remote machine' and swap which HoloLens device we had connected to the USB on the PC we were working on.
===
This post provided as-is with no warranties and confers no rights. Using information provided is done at own risk.
(Daddy, what does 'now formatting drive C:' mean?)
Hey Patrick,
I have followed your instructions to use a single PC running the SharingService and deploy from there onto two HoloLenses. This was a successful deployment, I see both devices have joined the shared session.
I am now getting Room deserialization errors which crash the deployed executable running on the second HoloLense to join the session. I will try the suggestions listed on this related thread to address the failure.
In the meantime, I consider this thread resolved.
Thank you so much for your prompt and helpful advice.
Best regards,
Sally
great! Do start another thread if you are still having issues deserializing. I don't know of any crashes.
===
This post provided as-is with no warranties and confers no rights. Using information provided is done at own risk.
(Daddy, what does 'now formatting drive C:' mean?)
I have the same problem, unsuccessfully trying to connect hololens to pc running sharing service.
I follow all steps in tutorial, then try to use completed project but it not working.
Sharing service gives me this three addresses:
172.16.80.1
172.18.18.26
169.254.80.80
I copy and paste it one by one at Server Address field in sharing prefab, it work in editor, but not work in hololens.
I don't understand why it doesn't work. Any ideas or suggestions?