HTC Vive Pro controllers are not being tracked

[jorgejgnz]

Describe the issue

According with documentation for MRTK 2.6, many controllers, such as HTC Vive Knuckles and HTC Vive Wands, will work natively once an application built with MRTK is launched on the compatible device.

After installing XR Plug-in Management package and after setting OpenXR and OpenVR (once imported SteamVR asset) as plug-in providers, headset is being tracked but controllers are not tracked or, at least, any gameobject related with controllers is instantiated in the scene.

MRTK singleton is configured with DefaultXRSDKConfigurationProfile but I'm getting the same result (only headset being tracked) with DefaultOpenXRConfigurationProfile.

The expected result is both headset and Vive Wands controllers being tracked natively using default or built-in configuration profiles.

I wonder if there are some missing package or some extra step I may have not considered.

Feature area

• Cross Platform
• OpenXR
• OpenVR

Additional context

Our project is running on Unity 2020.3.8f1.

[bruhnth17]

I have the same issue, using Unity 2019.2.14f1 and MRTK 2.6.1 @jorgejgnz did you make any progress yourself?

[bruhnth17]

8835 is related

[keveleigh]

@jorgejgnz Can you please double check on OpenXR that the HTC Vive Controller Profile is listed in your Interaction Profiles?

The OpenXR runtimes should still track these controllers without the explicit profile being present, but there's a bug we're investigating on either the Unity-side or the runtime side that it doesn't seem to be happening as-expected.

[eusebiu]

8835 is related

Just FYI: That is using XR SDK, not OpenXR

[stale[bot]]

This issue has been marked as stale by an automated process because it has not had any recent activity. It will be automatically closed in 30 days if no further activity occurs. If this is still an issue please add a new comment with more recent details and repro steps.

[NoTuxNoBux]

Could it be that the OP is trying to build for the Android target? I have an HTC Vive Focus 3 here for testing (untethered), which I build for using Android, and it's not possible to add the "HTC Vive Controller Profile" for the Android target; it simply doesn't show up, it only does for desktop and other profiles.

Is it possible that this controller support only works with streaming VR when the content is being ran on a desktop instead of the target device (i.e. Android)? The MRTK Controller Mapping profiles also don't seem to show any HTC Vive controllers. For the Quest it's different, because there seem to be custom interaction profiles for those controllers.

I had the same problem with a Pico Neo 3 Pro (also untethered) I used for testing earlier: I can get my MRTK app to start on both devices just fine, and on the Pico head gaze even works, but controllers and hand tracking won't work even after fiddling with a bunch of settings.

Granted, this was using PicoXR and WaveSDK XR as back ends, not OpenXR, as OpenXR is completely broken for me (might be due to my settings), but I noticed this in the OpenXR project settings anyway.

[IssueSyncBot]

We appreciate your feedback and thank you for reporting this issue.

Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.

Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.

Please note that MRTK3 was released in August 2023. It features an all new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visithttps://www.mixedrealitytoolkit.org.

Thank you for your continued support of the Mixed Reality Toolkit!