Since I updated my HoloLens2 Unity Project to Unity 2020.3 my deployed HoloLens2-Application (in Unity Editor they never happen) always throws the following Exceptions :
Could not create a device for 'Hand - Right (XRInputV1)'
(Exception: System.ArgumentException: Expected control positionAccuracy to be of type 'AxisControl' but is of type 'IntegerControl' instead;)
at UnityEngine.InputSystem.InputControll
Could not create a device for 'Hand - Left (XRInputV1)'
(Exception: System.ArgumentException: Expected control positionAccuracy to be of type 'AxisControl' but is of type 'IntegerControl' instead;)
at UnityEngine.InputSystem.InputControll
Does anybody know, how to get rid of those Exceptions?
I am using the MixedRealityToolkit 2.7.3 HoloLens2 default Configuration and noticed this problem at Unity Versions 2020.3.8, 2020.3.22 and 2020.3.26. Thanks in advance.
Best Regards !
CodePudding user response:
Firstly, please double check the MRTK Input profile setting. You can easily configure the project in Unity Menu: Mixed Reality > Toolkit > Utilities > Configure Project for MRTK
Then, please check out your XR setting, Since you are using Unity 2020.x, you can use OpenXR plugin, see Choosing an XR configuration.
If the issue is still there, this may also be caused by your hand control code. Here is discussion with the same exception as yours, see WikkidEdd's reply in this github issue. In their case, they need to use IntegerControl instead of AxisControl.
CodePudding user response:
Thank you for your Answer.
I wanted to use the OpenXR approach and was able to install the basic OpenXR-plugin from Unity Registry but if I select it in the XR Plug-In Management I need the corresponding "Microsoft HoloLens feature group".
Unfortunately I currently have no internet access on my developement computer and until now I was not able to find any downloadable package for this on the internet.
Can you tell me where I can download the OpenXR HoloLensFeatureGroup?
That would help me a lot and maybe it will also fix my problem as you said. If not, I will wait for the next MRTK Update as mentioned in the github issue where they mentioned to have it fixed.
