Search Issue Tracker
Third Party Issue
Votes
0
Found in [Package]
1.2.8
1.6.0
Issue ID
OXRB-108
Regression
No
[WMR] OpenXR XrSessionState not reported as expected when WMR headset set as OpenXR runtime
Reproduction steps:
1. Open user attached project “User Presence Testing.zip”
2. Open Assets > Scenes > SampleScene
3. Make sure that the WMR headset is set as OpenXR runtime
4. Enter Play mode
Expected result: Text shifts from “Present” and “Not Present” depending if sensors are triggered
Actual result: Text stays as “Present”
Reproduced with: 1.2.8 (2020.3.20f1), 1.6.0 (2020.3.43f1, 2021.3.16f1, 2022.1.24f1, 2022.2.2f1, 2023.1.0a23)
Reproducible on: Windows 11, WMR OpenXR
Not reproducible on: Steam VR OpenXR
Notes:
* In build the same issue, only text always shows “Not Present”
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note:
Unity is not able to fix this issue. Currently there is no OpenXR Extension to expose user presence data. The difference you see between runtimes is because Microsoft reports session states differently. We have shared your feedback with Microsoft, but we encourage you to reach out to them on their forums as well.