Search Issue Tracker
Fixed in 1.3.0
Votes
0
Found in [Package]
1.1.0-pre.5
Issue ID
1340793
Regression
No
On-Screen Button errors on mouse down/up when its Control Path is set to "Control [Keyboard]"
Reproduction steps:
1. Open the attached "Ctrl.zip" project
2. Open the "SampleScene" Scene
3. Enter Play Mode
4. In Game view, click on the Image
Expected result: No errors
Actual result: NotImplementedException (1.0.2) or NotSupportedException (1.1.0-pre.5) errors
Reproducible with: 1.1.0-pre.5 (2019.4.28f1, 2020.3.13f1, 2021.1.13f1, 2021.2.0b1)
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Resolution Note (fix version 1.3.0):
Fixed in 1.3.0 by https://github.com/Unity-Technologies/InputSystem/pull/1440