Hello everyone.

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.

Sharing service documentation

Where can I find further documentation on the sharing service? The readme in the repo for the sharing service list a bunch of features like lobbies, VOIP, etc but no documentation on how to use them.
Also this post seems to indicate that we can deploy this service on Azure, is there any official documentation regarding this?

Answers

  • ContextVRContextVR ✭✭✭

    Have you done the Shared Holograms tutorial yet?
    https://developer.microsoft.com/en-us/windows/holographic/holograms_240

  • I'll be honest.

    We haven't documented this very well yet. :)

    You can get the gist of lobbies from the Shared Holograms tutorial.

    I'll be even more honest...

    If I were creating a shared experience I planned to ship, I would probably use the Photon Unity Networking rather than the Holograms 240 service. At least at the moment, the sharing service requires us to set flags that will fail when submitting to the Windows store. Also, while you can deploy the sharing service to Azure, you will be highly reliant on knowing the IP address in Azure. Photon (and Unity's networking) have more robust discovery infrastructure implemented.

    I might also consider the networking built into Unity, but my experience and anecdotes from others has been that the built in networking tends to break when Unity updates. I had good luck with Photon the last time I tried it.

    ===
    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?)

  • When will the community receive more documentation?

  • I still would provide reference code for both Photon and Unity UNET--UNET will be the One True Way to network once Unity gets its act together. I mean, basically EVERYTHING in Unity breaks every time there is an update anyway....at least with 5.x. We just have to live with that.

    ralphbarbagallo.com - flarb.com - @flarb

  • Bump for interest

    Stephen Hodgson
    Microsoft HoloLens Agency Readiness Program
    Virtual Solutions Developer at Saab
    HoloToolkit-Unity Moderator

  • I am curious about the flags that need to be set that would fail submission. We have a couple of builds that have been accepted in the store (though not published) that include all of our sharing code. I am curious if ours succeeded because it is only setup for local connections or if the issue that was causing it to fail submission is no longer an issue.

    Taqtile

Sign In or Register to comment.