Search Issue Tracker
Fixed in 1.0.0-preview.2
Votes
0
Found in [Package]
preview - 0.2.10, preview - 1.0.0
Issue ID
1187185
Regression
No
Can't interact with the UI when the "Input System UI Input Module" and "Player Input" components share the same action map
How to reproduce:
1. Open the attached project ("case_1187185-Project.zip")
2. Open the SampleScene in the Scenes folder
3. Enter the Play Mode
4. Click on any of Button
Expected result: Button is interactable
Actual result: Can't interact with the Button
Reproduced in Unity versions: 2019.2.9f1, 2019.3.0b6, 2020.1.0a8
Reproduced in Package versions: "preview - 0.2.10", "preview - 1.0.0"
Couldn't test with Unity versions: 2017.4.33f1, 2018.4.11f1 (Packages don't have the required components)
Couldn't test with Package versions up to "preview - 0.2.8" (Errors)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.0.0-preview.2):
Fixed in 1.0.0-preview.2, available from Unity 2019.1