Search Issue Tracker
Fixed
Fixed in 1.5.3
Votes
0
Found in [Package]
1.4.1
Issue ID
OXRB-24
Regression
No
XRInputSubsystem.TryGetBoundaryPoints returns incorrect boundary positions with OpenXR plugin
Reproduction steps:
1. Measure your Room Scale play area dimensions set in Quest (physically or in a third-party app like SteamVR)
2. Open the attached project "repro.zip"
3. Build & run SampleScene or enter Play Mode with Quest connected via Link
4. Notice Debug.Log values in the Console
Expected result: With an example playspace dimensions of 1m x 1m, the values from TryGetBoundaryPoints methods are returned as follows: (0.5, 0, 0.5); (0.5, 0, -0.5); (-0.5, 0, -0.5), (-0.5, 0, 0.5)
Actual result: The values from TryGetBoundaryPoints methods are returned as follows: (1, 0, 1); (1, 0, -1); (-1, 0, -1), (-1, 0, 1)
Reproducible with: 1.2.8 (2020.3.31f1), 1.3.1 (2020.3.31f1, 2021.2.16f1, 2022.1.0b12, 2022.2.0a9)
Could not test with: 2019.4.37f1 (OpenXR plugin is not available)
Notes:
The user has reported that this also reproduces with HTC Vive
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
Add comment