Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.11.2
Issue ID
ISXB-1205
Regression
No
Player Input Component picks different control scheme than the default one
How to reproduce:
1. Open the “IN-88786_repro“ project
2. Open the SampleScene
3. Enter Play Mode
4. Select the “Cube“ GameObject
5. In the Inspector, observe the Debug section of the Player Input Component
Reproducible with: 1.7.0 (2021.3.46f1), 1.11.2 (2022.3.52f1, 6000.0.28f1, 6000.1.0a5)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Notes: The Scheme does change when using a different controller
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
The Input System Settings in this project does not include Mouse as supported device which is a default requirement for KeyboardMouse.
As KeyboardMouse control scheme does not meet all required devices, the next control scheme in the list with no required or optional devices becomes the best match - Xbox Controller.
If it is desired to have a project which does not support mouse, the KeyboardMouse control scheme should be updated to make Mouse non-required or add a new Keyboard only control scheme.