Search Issue Tracker
Fixed in 2017.1.0f3
Fixed in 5.5.X, 5.6.X
Votes
1
Found in
5.5.0f3
Issue ID
875834
Regression
No
[UWP] OnButtonClick() gets triggered multiple times before releasing Xbox One Controller button A
Steps to reproduce:
1. Open attached project
2. Build for WSA Universal 10 SDK
3. Open VS solution
4. Deploy on local machine
5. Hower over "Scene2" button with mouse
6. Press/hold A button on Xbox One Controller
Expected result: OnButtonClick() is triggered only once before releasing button A
Actual result: OnButtonClick() is triggered multiple times before releasing button A
Not reproducible on Editor, Windows Standalone
Reproducible with: 5.5.0b1, 5.5.1p2, 5.6.0b6
Comments (2)
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
- “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
nyarsulik
Nov 08, 2018 02:45
This is happening to me using 2018.2.14f1. It doesn't do this in editor, but in VS and then further in Xbox One my game is unplayable while two controllers are connected. When only one controller connected this works fine, no problems. The second I connect a second controller, all input fires multiple times in one press, like it is triggering on the "press" and then repeating like crazy.
pumpkinszwan
Mar 24, 2017 01:05
Workaround:
Add a check to ensure a small delay between handling button clicks in the UI. When a button click is detected, check that it has been at least ~0.2 seconds since a button click was handled, otherwise do not action the button click.
Since the issue mainly affects buttons that navigate between scenes, this delay will not affect responsiveness, but does eliminate the problem.