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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note (fix version 1.3.0):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1438.