Search Issue Tracker
Fixed
Fixed in 1.4.4
Votes
7
Found in [Package]
1.4.1
Issue ID
ISXB-254
Regression
Yes
[Input System] Some Input Actions are not received when using Input System 1.4.1
How to reproduce:
1. Open the attached project "InputSystem1.4.zip"
2. Connect the gamepad
3. Open the “SampleScene” scene
4. Enter the Play mode
5. Press each of the following buttons:
Gamepad:
Fire1: Button South
Fire2: Button East
Fire3: Button West
Fire4: Button North
Keyboard:
Fire1: Control
Fire2: Shift
Fire3: Alt
Fire4: Space
Expected result: Fire1 to Fire4 are all counted
Actual result: Fire4 for keyboard input and Fire1 for gamepad input are not counted
Reproduced on: 1.4.1 (2020.3.37f1, 2021.3.7f1, 2022.1.10f1, 2022.2.0b2, 2023.1.0a4)
Not reproduced on: 1.3.0 (2020.3.37f1, 2021.3.7f1, 2022.1.10f1, 2022.2.0b2, 2023.1.0a4)
Tested with: XBOX 360 For Windows Controller
Reproduced with: Windows 11
Note:
- This does not occur if "FreeCam" in Actions.inputactions is deleted
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (fix version 1.4.4):
Fixed in: Input System 1.4.4