Search Issue Tracker
Fixed
Fixed in 1.4.4
Votes
0
Found in [Package]
1.4.4
Issue ID
ISXB-356
Regression
No
When rebinding input, submit is not responsive when switching devices
How to reproduce:
1. Connect a controller to the PC
2. Open the attached project “InputBugTest.zip“
3. Enter the Play mode
4. Press the “Enter” key on the keyboard
5. Press the “K” (or any key) on the keyboard. Prompt and console should indicate that the fire action is now bound to “K”
6. Press the “Enter” key on the keyboard
7. Press any key on the controller
8. Press the “Enter” key on the keyboard
Expected result: Pressing the “Enter“ starts the rebinding of the “fire“ action
Actual result: Pressing the “Enter“ key gives no response
Reproducible with: 1.0.0, 1.4.4 (2020.3.42f1), 1.4.4 (2021.3.15f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0a22)
Couldn’t test with: 1.0.0-preview.7 and lower - Setting the Input system package’s version lower complete resets all of the Input System UI Module’s bindings and actions
Reproduced on: Windows 10 Enterprise
Notes:
- Reproduced with: PS5 DualSense, Xbox One and PS4 DualShock controllers
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
- Shader Graph Swizzle Node Input/Output and Mask Update Incorrectly After Undo
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
Resolution Note (fix version 1.4.4):
This is fixed in the latest version of the Input System.