Search Issue Tracker
By Design
Votes
1
Found in [Package]
1.3.0
Issue ID
ISXB-252
Regression
No
Player Input Default Scheme gets changed from Gamepad to Keyboard&Mouse when entering the Play Mode with Auto-Switch disabled
Reproduction steps:
1. Open the attached project
2. Select the "Player" GameObject in the Hierarchy window
3. Turn the Auto-Switch property off located under Player Input Component in the Inspector window
4. Enter Play Mode
5. Observe the text in the Game View
Expected result: The Input Scheme doesn't change and the text in the Game View says "Gamepad"
Actual result: The Input Scheme changes and the text in the Game View says "Keyboard&Mouse"
Reproducible with: 1.1.1, 1.2.0, 1.3.0 (2019.4.39f1, 2020.3.35f1, 2021.3.4f1, 2022.1.3f1, 2022.2.0a16)
Reproducible on: Windows 10 (21H2)
Note: The Input System ignores the Default Scheme property under Player Input Component whether the Auto-Switch property is on or off.
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Unfortunately, we weren't able to reproduce this issue with Auto Switch turned off and having a valid controller connected - the scheme shows up correctly as "Gamepad". (Tested using Input System 1.8.0-pre.2) The bug is either already fixed there or we don't have the right information for this issue, if you think that is the case and you're still having the issue on the latest version please let us know and we'll reopen the ticket for another look.