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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 1.3.0):
Fixed in 1.3.0 by https://github.com/Unity-Technologies/InputSystem/pull/1440