Search Issue Tracker
Not Reproducible
Not Reproducible in 1.2.X
Votes
0
Found in [Package]
1.2.0
Issue ID
XRHB-35
Regression
No
Controller tracking stops when using MetaXRFeature
As of the V51 integration asset it is possible to compile builds using the Meta XR Feature. The XR hands package should work with the oculus integration asset.
When using the MetaXRFeature on Quest 2, starting an app with controllers, switching to hands, and then switching back to controllers results in controllers not reporting as tracked anymore.
Expected behavior: controllers should continue to be tracked when an app switches from controllers, to hands, and back to controllers.
Comments (1)
-
prawn-star
Nov 25, 2023 01:00
I can confirm this is also the issue with XR Hands 1.3.0
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
Not reproducible anymore
Resolution Note (1.2.X):
Not reproducible anymore