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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Resolution Note:
Not reproducible anymore
Resolution Note (1.2.X):
Not reproducible anymore