Search Issue Tracker
Active
Under Consideration for 1.14.X
Votes
0
Found in [Package]
1.14.1
Issue ID
ISXB-1626
Regression
No
[Input System] The Device window in the Input Debugger is broken when opening it after the device was disconnected and reconnected
Steps to reproduce:
1. Open the “IN-108554” project
2. Open the Window -> Analysis -> Input Debugger
3. Connect the wireless controller
4. Open the controller Device window (click on the device)
5. Close the Editor
6. Disconnect the controller (remove in Bluetooth settings) and reopen the project
7. Close the controller Device window
8. Reconnect the controller and reopen the controller Device window
Expected result: Shows the controller input debugger
Actual result: Shows only window controls
Reproducible with: 1.7.0, 1.14.1 (6000.0.54f1, 6000.1.13f1, 6000.2.0b11, 6000.3.0a3)
Testing environment: Windows 11
Not reproducible on: macOS 15.5(M4 Pro)
Notes:
- Disconnecting and reconnecting the controller again fixes the issue
- Does not reproduce when not closing the controller Device window before reconnecting the controller
- Not reproducible with wired controller
- Sometimes it requires multiple attempts to reproduce
- 2 NullReferenceException errors in “UnityEditor.HostView.GetExtraButtonsWidth” (by user)
- Tested with Xbox Series controller
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
Add comment