Search Issue Tracker
Fixed in 1.1.1
Votes
5
Found in [Package]
1.1.0-preview.1
Issue ID
1272521
Regression
No
[Input System] Disabled Input System UI Input Module doesn't become enabled when the currently enabled Module is removed
How to reproduce:
1. Open the attached "1272521 repro" project
2. Open the "A" Scene from Assets > Scenes
3. Enter Play Mode
4. Press the "Space" key on the keyboard
5. Click the Button in the middle of the Game window
Expected results: the Button is clicked successfully
Actual results: the Button is unclickable
Reproducible with: 0.2.10-preview (2020.2.0b1), 0.9.0-preview (2020.1.4f1), 1.0.0 (2019.4.9f1, 2020.2.0b1), 1.1.0-preview.1 (2019.4.9f1, 2020.2.0b1)
Could not test with: 0.1.2-preview (2019.4.9f1, compilation errors)
Notes:
-Turning on the Debug mode on the Inspector window and selecting the "EvenSystem" GameObject in the "B" Scene after the 4th step will reveal that the "Owns Enabled State" variable is set to false
-The same behavior can be observed in the "C" Scene where disabling/deleting the "EventSystem (main)" GameObject leaves the button unresponsive since the other Input System UI Input Module, present in the Scene, doesn't become active
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment