Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.1.0-pre.5
Issue ID
1340125
Regression
No
[Input System] Gamepad input isn't tracked after switching control schemes
How to reproduce:
1. Open the user's attached project "InputSystemTest.zip"
2. From the Project tab, open Assets/SampleScene.unity and make Game View visible
3. Connect a gamepad to the computer
4. Enter Play Mode
5. Move the left joystick around and see how values change in Game View
6. Move the mouse around and see how values change in Game View
7. Move the left joystick around again
Expected results: current control scheme is set to Gamepad and values coming from the gamepad input can be seen in Game View
Actual results: current control scheme is set to Gamepad, but the values don't change and the last known value from mouse input can be seen in Game View
Reproducible with: 2019.4.28f1, 2020.3.11f1, 2021.1.10f1, 2021.2.0a19 (Input System 1.0.2, 1.1.0-pre.5)
Could not test with: 2018.4.35f1 as it requires outdated versions of Input System
Notes:
- Tested with an Xbox One controller
- Also reproducible on Windows Standalone builds
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
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
Resolution Note:
Project sets up one input path with "Generate C# Class" and one with PlayerInput. The former needs manual configuration to work with control schemes.
Work is planned both to more closely align the two approaches and two improve the out-of-the-box setup that "Generate C# Class" creates.