Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.4.0
Issue ID
ISXB-129
Regression
No
Controllers are not detected in player when plugged in before the Splash Screen is shown, but after the Player boots up
How to reproduce:
1. Open the attached project "ControllerBug.zip"
2. Open the Build Settings (File > Build Settings...)
3. Build And Run
4. Plug in the controller as soon as the Player boots up, but before the Unity logo Splash Screen shows up
Expected result: The controller is detected and is usable
Actual result: The controller is not detected and is unusable
Reproducible with: 2019.4.38f1, 2020.3.34f1, 2021.3.2f1, 2022.1.0f1, 2022.2.0a13
Tested with: Xbox One controller (USB C), Dual Sense controller for PS5 (USB C)
Notes:
- The controller is still not detected after unplugging it and plugging it back in
- The issue only appears when plugging in the controller at the right time
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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
There are no fixes planned for this Bug