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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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.