Search Issue Tracker
Active
Under Consideration for 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.
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
- Asset Bundles retain their previous hash and CRC values when an object within a bundle is changed and rebuilt
- APV Reflection Probe Normalization breaks when SSGI is enabled
- Default Custom Components in project have Library counterparts
- [iOS]"The destination host has an erroneous SSL certificate" error is thrown when using UnityWebRequest to connect to the server with a self-signed certificate
- Freeze/crash on DynamicHeapAllocator::Allocate when opening a specific project
prawn-star
Nov 25, 2023 01:00
I can confirm this is also the issue with XR Hands 1.3.0