Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.1.0-preview.3
Issue ID
1326095
Regression
No
[Input System] PlayerInput.Instantiate pairs all devices with the same control scheme to one user
How to reproduce:
1. Open the attached project "unity-bug-1326095-main.zip"
2. From the Project tab, open Assets/Scenes/SampleScene.unity
3. Connect two PS4 controllers (or other controllers with the same control scheme)
4. Enter Play Mode
5. Press any button on one of the controllers
6. Open Window > Analysis > Input Debugger and observe Paired Devices under User #0
Expected results: only one controller (the one that was used in step 5) is added to Paired Devices of User #0
Actual results: both controllers are added to Paired Devices of User #0
Reproducible with: 2019.4.25f1, 2020.3.7f1, 2021.1.6f1, 2021.2.0a16 (Input System 1.0.2, 1.1.0-preview.3)
Could not test with: 2018.4.34f1 as it requires outdated versions of Input System
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
- Shader warnings are being thrown after building Mixed Reality Template
- Error is thrown when entering play mode with build profiles docked and standalone profiler open
- The Player hangs when activating another maximized application
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
- Crash on RtlLookupFunctionEntry when using 10 or more GameObjects with Articulation Body component in the scene
Resolution Note:
Control scheme specifies three gamepads, all optional. Pairing logic will grab as many as it can. This is the same logic that grabs both a keyboard *and* a mouse even if just the keyboard is used.
The list of devices in the control schemes is not "any one" but "all of these".