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
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
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