Search Issue Tracker
Fixed
Fixed in 1.14.1
Votes
2
Found in [Package]
1.14.0
Issue ID
ISXB-1555
Regression
Yes
[Input System] TrackedPoseDriver stops tracking with Input System 1.14.0 if active before XR device initialization
Steps to reproduce:
1. Open the attached user's project "InputSystemPoseDriverIssue.zip"
2. Connect Meta link to Quest 2/3
3. Make sure you are on Input System 1.13.1 and the TrackedPosedDriver is enabled under the "Sphere" GameObject
4. Enter Play Mode and observe the right controller is tracked
4. Update to 1.14.0 and enter Play Mode, observe the Sphere GameObject on the right controller no longer is tracked
Expected Results: TrackedPoseDriver continues tracking even if it's active before XR device initialization
Actual Results: TrackedPoseDriver stops tracking with Input System 1.14.0 if active before XR device initialization
Reproducible with: Input System 1.14.0 (2021.3.52f1, 2022.3.62f1, 6000.0.49f1, 6000.1.4f1, 6000.2.0b3)
Not reproducible with: Input System 1.13.1 (2021.3.52f1, 2022.3.60f1, 6000.0.44f1, 6000.1.0b12, 6000.2.0a7)
Environment tested: Windows 11 24H2
Reproducible with these devices:
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
VLNQA00417 - Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, OS: 10
Notes:
-Workaround is to deactivate and activate TrackedPoseDriver after XR is initialized
-The issue is not exclusive to VR devices, it can also be reproduced on Android devices (e.g Google Cardboard)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment