Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.4.1
Issue ID
ISXB-260
Regression
Yes
Input system regression: Rebinding axis returns just axis instead of button
How to reproduce:
1. Open the attached project “Input System Axis Bug.zip”
2. Open the “SampleScene“ Scene
3. Enter the Play mode
4. Connect a gamepad
5. Press the X button (PlayStation gamepad) or the A button (Xbox gamepad)
6. Move the left analog stick up
Expected result: Rebinding the axis returns “<Gamepad>/leftStick/up“ - returns the button that’s been bound
Actual result: Rebinding the axis returns “<Gamepad>/leftStick/y“ - returns the axis itself and not the button
Reproducible with: 1.4.1 (2020.3.37f1, 2021.3.8f1, 2022.1.12f1. 2022.2.0b3, 2023.1.0a4)
Not reproducible with: 1.3.0 (2020.3.37f1, 2021.3.7f1, 2022.1.11f1, 2022.2.0b3, 2023.1.0a3)
Couldn’t test with: 1.3.0 (2021.3.8f1, 2022.1.12f1, 2023.1.0a4) - package version is unavailable
Reproduced with: Windows 10 Enterprise, MacOS Monterey 12.3.1
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:
Rebinding axis composite positive/negative controls should be matching axes in principle, and we do treat buttons as axes also.
To match up/right/bottom/left buttons please use WithExpectedControlType("Button") with the rebinding request.