Search Issue Tracker
Fixed in 1.17.0-pre.2
Votes
2
Found in
1.16.1
Issue ID
UUM-131166
Regression
No
Connecting a controller causes a "Could not create a device" error when XR is set up in the project
How to reproduce:
1. Open the "IN-88774_repro" project
2. Connect a DualSense controller to the device
3. Observe the Console
Expected result: No errors are seen
Actual result: "Could not create a device" error is seen
Reproducible with: 1.9.0 (6000.0.27f`1), 1.11.2 (6000.0.27f`1, 6000.1.0a4)
Could not test with: 2021.3.45f1, 2022.3.52f1 (incompatible packages)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Note: Also reproducible with Xbox controller
Error: Could not create a device for 'Sony Interactive Entertainment DualSense Wireless Controller (HID)' (exception: System.InvalidOperationException: Cannot instantiate device layout 'Dpad' as child of '/DualSenseGamepadHID'; devices must be added at root
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.17.0-pre.2):
The issue will be fixed in OpenXR package 1.17.0-pre.2. Also will be included in the future 1.17.0 verified release version.
Resolution Note:
The issue will be fixed in OpenXR package 1.17.0-pre.2. Also will be included in the future 1.17.0 verified release version.