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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment