Mixedrealitytoolkit-unity: NullReferenceException in ControllerFinder.OnEnable when using the HoloLensCamera
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
davidkline-ms
All 7 comments
The HoloLens camera prefab is depreciated.
Probably best to remove.
StephenHodgson
on 7 May 2018
@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)
davidkline-ms
on 8 May 2018
People shouldn't be removing things from prefabs anyway.
StephenHodgson
on 8 May 2018
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).
keveleigh
on 8 May 2018
@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.
davidkline-ms
on 10 May 2018
Yup, that's why we're taking the configuration profile approach in vNEXT.
StephenHodgson
on 10 May 2018
This was released in the 2017.4.0.0 release candidate
davidkline-ms
on 25 May 2018
Related issues
brean
路
3Comments
provencher
路
3Comments
nrchuanqi
路
3Comments
matatabi-ux
路
3Comments
chrisfromwork
路
3Comments
Most helpful comment
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).