Search Issue Tracker
Fixed
Fixed in 1.6.0
Votes
0
Found in [Package]
1.5.0
Issue ID
OXRB-74
Regression
No
[OpenXR][Input System] PoseControl in InputSystem.XR and PoseControl in OpenXR conflict
Reproduction steps:
1. Open the attached user's project "PoseControlRepro.zip"
2. Enter Play Mode
3. Check Console Window
Expected result: No argument exception and PoseControl in InputSystem.XR and PoseControl in OpenXR do not conflict with each other
Actual result: "ArgumentException: Expected control 'pose' to be of type 'PoseControl' but is of type 'PoseControl' instead\!" is printed in the Console window
Reproduces on: Input System 1.1.1 - 1.3.0 (2020.3.34f1, 2021.3.2f1, 2022.1.1f1, 2022.2.0a15)
Could not test on 2019.4.39f1 due to OpenXR not being available and below Input System 1.1.1 due to package errors
Notes:
-For a more detailed description, check the "PosecontrolRepro.cs" in the project
-
BenIVRE
Feb 21, 2024 16:13
Still an issue in OpenXR 1.7.0 and InputSystem 1.7.0
-
HarsanyiT
May 18, 2023 14:36
*Open XR 1.6.0
-
HarsanyiT
May 18, 2023 14:34
It's not fixed. Strange, but not always happening for me. Somewhere around 50% of the starts are drops the error.
Unity 2022.1.5f1, OpenXR 0.16.0, XR Interaction Toolkit 2.2.0
-
Phenotype
Apr 11, 2023 17:24
I still get this issue in OpenXR Plugin 1.7.0
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 (fix version 1.6.0):
Fix released in OpenXR package 1.6.0