Mixedrealitytoolkit-unity: Structuring and extending the MRTK UNET components and example

[FejZa]

Overview

The current "SharingWithUNET" example is basically everything there is concerning UNET. I've been using UNET for all my shared experiences on HoloLens and WMR devices and think there is a lot of potential for reusable components and better documentation here.

The current example contains components / code that can be made reusable and useful for any UNET based project. I'd suggest creating a "SharingWithUNET" folder in the MRTK, analog to the current "Sharing" folder. Refactor the example and move components not specific to the example itself into the new MRTK UNET folder.

Why is this useful?

• Developers who chose to use UNET get a headstart using MRTK prefabs and components for UNET
• The example becomes more lightweight
• These changes provide a base for futher UNET contributions. I have a lot of code / components from past projects I'd like to get into the MRTK that help with UNET. But right now, I just don't know where to start and where to add them.
• The current UNET code / components are not well structured and really hard to separate into logic pieces. This is a chance to refactor some of the code and have clear responsibilities.

[StephenHodgson]

UNET is a core editor component and has lots of really good tutorials and code snippet examples all over the web, and developers use different features depending on their needs, so we decided to remove some of the examples from the project.

Also the examples weren't well maintained, but they do exist in the examples package of each release.

That being said, there are plans to review and reimplement the sharing service and UNET in vNEXT.

[FejZa]

So is there any way to get involved or to know what the plans are?

[StephenHodgson]

https://github.com/Microsoft/MixedRealityToolkit-Unity/projects/5#card-9450839

[FejZa]

Thanks Stephen!

[StephenHodgson]

Having this conversation automatically makes you involved 😉.

Most of our communication about updated features and porting happens either here on Github or in the Community Slack channel.

You're more than welcome to PM me there and open new Pull Requests against the vNEXT branch.

[HeadClot]

Hey - With unet being deprecated. What is the plan for this issue going forward?

There are Community maintained versions of unet below.

https://github.com/vis2k/Telepathy Low Level API
https://github.com/vis2k/Mirror/ High Level API

[StephenHodgson]

Likely not. We're looking at using webRTC or Photon for our new initial sharing offerings in vNEXT

[jwittner]

Deprecation has been delayed, and UNet HLAPI will be moved to a package: https://forum.unity.com/threads/unet-deprecation-thread.543501/

New API, in Alpha, looks terribly unready: https://github.com/Unity-Technologies/multiplayer

[bengreenier]

Hey folks, a proposal for some webrtc work that could eventually morph into a larger solution (note: this is just my personal opinion) addressing the above can be found in #3590 - cross-linking for context.

[Yoyozilla]

Bulk closing older HTK bug. Please reopen if you can repro this issue in MRTK v2.
Thanks!
Yoyo