Mixedrealitytoolkit-unity: Type or namespace not found errors in ArticulatedHand.cs

[genereddick]

Overview

Trying to build with latest code throws errors from missing types or namespaces in ArticulatedHand.cs. Error doesn't appear in editor as breaking code is wrapped in a directive block:

#if WINDOWS_UWP

Expected Behavior

No errors

Actual Behavior

The type or namespace name... could not be found
HandJointKind
HandMeshObserver
JointPose

Steps to reproduce

_(Links to sample github project preferred)_

Unity Editor Version

2018.3.11f1

Mixed Reality Toolkit Release Version

mrtk_development latest

[keveleigh]

https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/GettingStartedWithTheMRTK.html

A more recent SDK is required for MRTK v2. It's currently accessible as an Insider SDK (it does not require you to be running an Insider Windows build), but will be released as part of the next Windows release. A download link can be found in the documentation link above.

[genereddick]

OK, updated to 18362 build & Win SDK and that allowed the build to succeed, though Unity threw a whole bunch of errors, not sure what impact they have, or if they are Unity problems (removed them for now since they seem specific to this project, not happening elsewhere)

[wiwei]

We'll need to followup with unity on those issues - it looks like the latest version of unity + those new types aren't playing well together.

AFAICT however it doesn't seem to have any runtime impact.

[genereddick]

Errors stopped for me after some combination of reboot, restart Unity, delete and recreate Library folder, so with updating to 18362 it is working as expected.

[davidkline-ms]

Thank you for the update @genereddick. We will continue to investigate.

[frangagn]

Any lines of code we could comment out in order to be able to compile our projects in the meantime? Very frustrating after days of development and debugging not to be able to compile our final product, especially when it's for mixed reality and has nothing to do with articulated hands...

[Yolo-Jerome]

How can this be fixed if using SDK 18362 is not an option?

HoloLens 1 curently runs on 17763 and there is no update available so I can't deploy a project built with SDK 18362 ... Does this mean MRTK 2.0 is still not suitable for HL1 ??

[keveleigh]

We have API checks around any 18362 API to prevent them from being called on a HoloLens 1.
You can deploy an app built for 18362+ on a device running a lower version of Windows as long as it's equal to / higher than the min app version. By default, I believe Unity sets the min to 10240.

Were you unable to deploy or run on an HL1?

[Yolo-Jerome]

@keveleigh

sorry already "fixed" it. I had to leave the Minimum Platform Version down at 10240for some reason (didn't work with e.g. 17763)

[andrewspalato]

Changing the minimum platform version and the target version to 'latest installed' fixed it for me.