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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 1.3.0):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1438.