Search Issue Tracker
Not Reproducible
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Not reproducible anymore