Search Issue Tracker
Fixed in 1.3.0
Votes
0
Found in [Package]
1.1.0-preview.1
Issue ID
1341740
Regression
Yes
ButtonControl.wasPressedThisFrame is false when using InputTestFixture.Press
How to reproduce:
1. Open the attached project's "case_1341740-Project.zip" Scene labeled "SampleScene"
2. Open the Test Runner (Window->General->Test Runner)
3. In the Test Runner window, run the "TestPress"
4. Wait for the test to finish
Expected result: ButtonControl.wasPressedThisFrame returns true and a message is logged in the Console
Actual result: ButtonControl.wasPressedThisFrame returns false and nothing is logged in the Console
Reproducible with: 1.1.0-preview.1, 1.1.0-pre.5 (2019.4.28f1, 2020.3.10f1, 2021.1.11f1, 2021.2.0a20)
Not reproducible with: 1.0.2 (2019.4.28f1, 2020.3.10f1, 2021.1.11f1, 2021.2.0a20)
Couldn't test with 2018.4.36f1 (Affected functions not available)
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 freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
- FrameTimingManager.GetLatestTimings adds background time to the next focused frame when the Player is unfocused
- PropertyDrawer gets disposed while still being active when adding a secondary component
Resolution Note (fix version 1.3.0):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1438.