Search Issue Tracker
Fixed in 1.1.1
Votes
1
Found in [Package]
1.1.0-pre.5
Issue ID
1359306
Regression
Yes
Input System uGUI Button does not react when clicked
How to reproduce:
1. Open the user's attached project
2. Open scene Scenes/SampleScene
3. Open the Game view and press the Play button
4. Mouse over the "Settings" button and click
Expected result: the button changes appearance on mouse hover, opens a new menu when clicked
Actual result: the button does not react to user input
Reproducible with: 1.1.0-pre.5, 1.1.0-pre.6 (2019.4.30f1, 2020.3.17f1, 2021.1.18f1, 2021.2.0b9, 2022.1.0a6)
Not reproducible with: 1.1.0-preview.3 (2019.4.30f1, 2020.3.17f1, 2021.1.18f1, 2021.2.0b9, 2022.1.0a6)
-
Rene-Damm
Aug 26, 2021 16:32
Comes back to a fix that landed in pre.5 which made the behavior in the editor and player consistent such that in both cases, AddComponent<InputSystemUIInputModule>() results in a blank UI input module without any connected actions. AssignDefaultActions() had to be called to put a default set in place.
We are tweaking this behavior for 1.1 final such that if an InputSystemUIInputModule is enabled without any actions, it assigns a default set implicitly.
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
- 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
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 1.1.1):
Fixed in Input System 1.1.1
InputSystemUIInputModule now creates a default action setup implicitly when added from code.