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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment