Mixed Reality support in Unity: compilation errors while building

[passervr]

Mixed Reality support seems to be working great in the Editor, but building it will result in many compilation errors.

Many error can be resolved by enabling the WSAPlayer platform for the dlls found in LeapMotion/Core/Plugins/, but many are still left.

Tested with:
- Unity 2017.2.1f1
- Leap Motion Core Assets v 4.3.4

Any forecast on when this could be solved?

[AlexColgan]

Unfortunately we don't have a Universal Windows Platform SDK, which would be required for Windows MR (since it basically runs inside a sandbox).

[passervr]

I don't think you need the SDK for this. It just seem to be some minor changes in the code. For instance: I get the following errors:
Assets\LeapMotion\Core\Scripts\DataStructures\Deque.cs(187,30): error CS1503: Argument 2: cannot convert from 'uint' to 'int'
Assets\LeapMotion\Core\Scripts\DataStructures\Deque.cs(187,51): error CS1503: Argument 5: cannot convert from 'uint' to 'int'
Which can easily be solved by changing the line

Array.Copy(_array, _front, newArray, 0, _count);

to

Array.Copy(array, (int)front, newArray, 0, (int)_count);

I believe error like this come forward because the files are linked to different .NET variants (see: https://stackoverflow.com/questions/13468864/error-cs0117-system-type-does-not-contain-a-definition-for-gettypecode for instance)

I had to do something similar myself in my Unity code to make my package (Humanoid Control) compatible with both SteamVR/Oculus and Mixed Reality.

[Jimbo1368]

Have you been able to fix the errors and export to Windows MR?