Search Issue Tracker
Fixed in 1.1.0-pre.6
Votes
0
Found in [Package]
1.1.0-preview.3
Issue ID
1327628
Regression
No
[Input System] Devices are reassigned to the wrong users after adding a new device
How to reproduce:
1. Open the user's attached project "BugTest.zip"
2. From the Project tab, open Assets/Scenes/SampleScene.unity
3. Enter Play Mode
4. In the Input Debugger (Window > Analysis > Input Debugger), expand the Users section until all users and their paired devices are visible
5. In the Game View, press the "Add Device" button
6. Repeat step 4
Expected results: a new gamepad Gamepad:/user0pad* is added to User #0, devices under the other users remain unchanged
Actual results: a new gamepad is assigned to User #0, but devices are reorganized and each user now has a Paired Device that doesn't belong to it (e.g. User #0 has Gamepad:/user2pad* assigned to it)
Reproducible with: 2019.4.24f1, 2020.3.4f1, 2021.1.3f1, 2021.2.0a12 (Input System 1.0.2, 1.1.0-preview.3)
Couldn't test with: 2018.4.34f1 as it requires outdated versions of Input System
Notes:
- The issue occurs in the Editor on both Windows and macOS
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.1.0-pre.6):
Fixed in Input System 1.1.0-pre.6, available in 2019.4.0f1 and above