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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment