Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.4.1
Issue ID
OXRB-31
Regression
No
Oculus Quest thumbstick upon release returns to zero values relatively slower on OpenXR
Reproduction steps:
1. Open the attached project "Oculus_joystick.zip"
2. In Assets/Scenes open SampleScene
3. In Window -> Analysis open Input Debugger
4. With Quest Link enabled enter Play Mode
5. In Input Debugger select OculusTouchControllerOpenXR
6. Scroll to the thumbstick values and move the Oculus controller thumbstick to the very right (1.0, 0.0) or left (-1.0, 0.0)
7. Release the thumbstick and observe its values in the Input Debugger
8. In packages change to Oculus XR Plugin and enable it in project settings
9. Repeat steps from 4 to 7
Expected result: Controller's thumbstick moves back to (0.0, 0.0) after releasing in OpenXR and Oculus XR Plugin almost immediately
Actual result: Controller's thumbstick returns to zero slower in OpenXR
Reproducible with: 1.2.8 (2020.3.31f1), 1.3.1 (2022.2.0a12), 1.4.1 (2020.3.33f1, 2021.3.1f1, 2022.1.0f)
Couldn't test with: 2019.4.38f1 (OpenXR package is not available)
Notes:
- As the difference (4-7 frames) is relatively hard to notice, recording both tests might be needed to compare (or watch the videos attached)
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
- 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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
There are no fixes planned for this Bug