Mixedrealitytoolkit-unity: Task vNext - Update WMR to use platform code for runtime

[SimonDarksideJ]

Overview

The Windows Mixed Reality Device / Controllers currently use the InteractionManager provided by Unity. This needs to be updated to enable use of the Windows.Spatial namespace in the player layer

Requires

• Updating the InteractionManager events and handlers to use the Windows.Spatial equivalents
• Building Controller assemblies that will rebuild and automatically wire up their references with the core MRTK assembly.
• Evaluating if any additional features are needed to support (or removal)
• Investigate possible refactoring options for Devices / Controllers

Acceptance Criteria

• [x] I can start Unity in UWP mode whilst configured to use the Windows Mixed Reality platform
• [x] I can view a scene in editor using an Windows Mixed Reality headset
• [x] I can visualize a default object as a controller
• [x] Input System actions are generated from the Windows Mixed Reality controller and sent to the Input System
• [x] All inputs from the selected controller are mapped to the Input System

[davidkline-ms]

We should be building on Unity, not replacing it. Right?

[SimonDarksideJ]

This is to use the Windows UWP Platform code (as demonstrated in the last shiproom with the "Player" projects) over Unity's implementation. Giving us greater freedom (and likely performance) over what is available today

[StephenHodgson]

I agree, we should be using the native platform code, so we don't have another layer to go through.

When we're done, we will be able to use the native platform code in the editor runtime as well.

[davidkline-ms]

Does this imply custom platform code for each device? Not having to write platform code for input, etc is one of the benefits of Unity.

I worry that we are duplicating effort that can best be used elsewhere in the project.

[StephenHodgson]

It will not, because of the way we've setup the Input Actions to be device agnostic.

[StephenHodgson]

I worry that we are duplicating effort that can best be used elsewhere in the project.

That was my same thoughts, but Simon is paranoid of Unity, lol.

[SimonDarksideJ]

This isn't implemented yet.
The aim is to replace the Unity "Interactionmanager" use with the Windows.Spatial namespace in the player project.

[davidkline-ms]

Thanks for clarifying, @SimonDarksideJ