NullReferenceException in ControllerFinder.OnEnable when using the HoloLensCamera

[david-c-kline]

This occurs due to there not being a motion controller attached to the camera.

The fix is to check whether or not the motion controller singleton has initialized rather than assuming it is safe to use the instance.

Mixed Reality Toolkit Release Version

2017.2.1.4

[StephenHodgson]

The HoloLens camera prefab is depreciated.

Probably best to remove.

[david-c-kline]

@StephenHodgson,

While I agree that the HoloLens camera should probably be removed, we should still harden the controller finder, in case someone removes the controller from the MixedRealityCamera prefab (ex: HoloLens only projects)

[StephenHodgson]

People shouldn't be removing things from prefabs anyway.

[keveleigh]

Using the MixedRealityCamera prefab will also cause this issue (though it might be good to deprecate that as well and narrow down to one configurable camera prefab instead).

[david-c-kline]

@StephenHodgson, it could be argued that if people are removing things (that they don't need or that their target platform does not support) from prefabs the prefabs have too much on them by default.

[StephenHodgson]

Yup, that's why we're taking the configuration profile approach in vNEXT.

[david-c-kline]

This was released in the 2017.4.0.0 release candidate