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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This is fixed in the latest version of the Input System.