Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2018.2.0a7
Issue ID
1019348
Regression
Yes
Input Up and Down events are triggered every frame
The input API's for GetButtonUp and GetButtonDown are being fired every frame, as though the input is being released regardless of if the button is actually being held down.
Reproduction Steps:
1. Build & Run the attached project
2. Press and hold X or A on a gamepad/joystick
3. Observe GetButton, GetButtonDown and GetButtonUp messages are constantly appearing every frame
Expected Result:
A single GetButtonDown should appear, along with constant GetButton messages, and finally GetButtonUp once the key is released.
Reproducible in version 2018.2.0a7.
Not reproducible in version 2018.2.0a6.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Add comment