Search Issue Tracker
Fixed in 1.1.0-preview.4
Votes
0
Found in [Package]
1.1.0-preview.3
Issue ID
1323566
Regression
No
Input System default UI actions do not register when adding InputSystemUIInputModule at runtime to an active Game Object
How to reproduce:
1. Open the attached project (case_1323566-InputSystem)
2. Click Play
3. Click anywhere in the Game View
Expected result: 'Clicked' is printed to the Console
Actual result: Nothing is printed to the Console
Reproducible with: 1.0.0 - 1.1.0-preview.3 (2019.4.23f1, 2020.3.2f1, 2021.1.1f1, 2021.2.0a10)
Workaround: Issue is not present when adding the InputSystemUIInputModule to a non-active Game Object
Notes:
1. Uncheck the Active checkbox of Bug Repro Script attached to GameObject to see the workaround
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.1.0-preview.4):
Fixed in Input System 1.1.0-pre.5 available in 2019.4 and up. Have to use the InputSystemUIInputModule.AssignDefaultActions() method to resolve the issue