Search Issue Tracker
Fixed in 1.0.0-preview.3
Votes
4
Found in [Package]
0.9.5, 1.0.0
Issue ID
1188666
Regression
Yes
[Input System] UI becomes unresponsive when multiple GameObject components reference the same InputActions asset
How to reproduce:
1. Open user-submitted project (Unity_ButtonFeedback_2019_3)
2. In 'Scene' scene disable the PlayerInput GameObject
3. Enter Play Mode
4. Hover the mouse over one of the buttons - the buttons get highlighted
5. Exit Play Mode, enable the PlayerInput GameObject
6. Enter Play Mode and hover the mouse over one of the buttons
Expected result: the buttons get highlighted
Actual result: nothing happens
Reproducible with: 2019.2.8f1, 2019.3.0b6, 2020.1.0a7
Could not test with: 2017.4.33f1, 2018.4.10f1(regressed package version unavailable)
Reproducible with package versions: 0.9.5, 1.0.0
Not reproducible with package versions: 0.9.4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerLoop.SetPlayerLoop() function is ignored when playing game in Player
- Lighting data is carried over from one Scene to another when changing Scenes in the Play Mode
- The <sprite> tag inserted image from a Sprite Asset into the UI Builder Button disappears when the Inlined Style Text Shadow Horizontal or Vertical Offset is set to be more than 0 px
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
Add comment