Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.0.0-preview.5
Issue ID
1205971
Regression
No
[New Input System] PlayerInput component ignores player input when using ControlScheme
Reproduction steps:
1. Open the attached project ("case_1205971-ControlScheme.zip")
2. Open the repro scene ("SceneWithControlScheme")
3. Enter Play Mode
4. Press 'Enter' key
5. Inspect Console output
Expected result: "Fired Player1" and "Fired Player2" logs are printed
Actual result: No logs are printed
Reproducible with: 2019.3.5f1, 2020.1.0b1, 2020.2.0a2
Couldn't test with: 2017.4, 2018.4 (required package versions are not supported)
Reproducible with package versions: 0.9.3, 1.0.0-preview.5
Note: Player Input works without issues when ControlSchemes are not used
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Resolution Note:
Control schemes need to list the devices they need in order for those devices to get paired to the player.