[BUG] Meta Quest Controllers incorrectly visualized with hands and has terrible performance

[Ali-Can-Keskin]

Describe the bug

When using the XRI3 branch of MRTK3 in Unity 6 on Meta Quest, controller visualization and performance are broken:

• Even when hands are active, controllers are still visualized inside the hands.
• When controllers are active, they update at an extremely low framerate (~5 FPS), making them nearly unusable.

To reproduce

Steps to reproduce the behavior:

1. Clone and open the XRI3 branch of MRTK3 in Unity 6.
2. Build and run the sample scene (or any MRTK3/XRI3 scene) on Meta Quest.
3. Enable hand tracking → controllers are still rendered inside the hands.
4. Switch to controller input → controller visuals appear, but update at ~5 FPS.

Expected behavior

• When hand tracking is active, controllers should not be rendered inside the hands.
• When controller input is active, controller updates should run at full framerate (smooth, not lagging).

Screenshots

You can check this video capture from Quest 3.

Video shows controllers being visualized inside the hands, and when switching to controller input, the controller updates appear at ~5 FPS instead of smooth motion.

Your setup (please complete the following information)

• Unity Version: Unity 6000.0.0b / Unity 6 (tested build)
• MRTK Version or Commit: MRTK3, XRI3 branch (please specify commit if available)

Target platform (please complete the following information)

• HoloLens 2
• Magic Leap
• OpenXR (Meta Quest)

[N0RAIR]

I can confirm this. Happened to me with similar setup.
This is very crucial to fix! Input has to work flawlessly!

[keveleigh]

I unfortunately don't have a Quest to test on, and it looks like the video link has expired. Would you be able to upload it again, please, @Ali-Can-Keskin?

[Ali-Can-Keskin]

I unfortunately don't have a Quest to test on, and it looks like the video link has expired. Would you be able to upload it again, please, @Ali-Can-Keskin?

now it should work again.

[RCrolyFex]

This has been bugging me for a while now, with some odd inconsistencies between what our build server made and what is produced locally.

Here's the settings what work for me, might be helpful for someone else:

The naming here is doing no-one any favours - might be useful to add where the packages are coming from - the validator will correctly flag this one up (although the message is not super clear tbh) This is what was causing the server to build differently, as by default the incorrect subsystem is selected, and any changes are lost when pushing to the server as the package was re-installed.

Could be a suggestion for MRTK to create a profile in assets when installed, rather than having the immutable profile as default; easy one to miss - the changes will be reflected locally, but lost as the packages folder is in the library and not tracked.

Still awaiting the build on the server here, and your milage may vary (FWIW I'm targeting Quest3 - still haven't gotten the correct controller to appear, but that's another days battle). Will report back if the server build works as intended, a local build with these settings does, and the jerky movement seen before is gone.