Search Issue Tracker
Fixed
Votes
0
Found in [Package]
2.2.0
Issue ID
1360882
Regression
Yes
[Device Simulator] UI elements are not responding to inputs when using Device Simulator with Player Input component
How to reproduce:
1. Open user attached project
2. Enter Play Mode
3. On the left of the Game view press button "Game" and select "Simulator"
4. In the Simulator view press on the button "Button"
Expected result: Button receives inputs
Actual result: Button does not receive inputs
Reproducible with: 2.2.0 - 3.0.2-preview (2019.4.30f1, 2020.3.19f1, 2021.1.0a1)
Not reproducible with: 2.1.1 (2019.4.30f1, 2020.3.19f1), Device Simulator package is built-in (2021.1.0a3, 2021.1.22f1, 2021.2.0b12, 2022.1.0a10)
Couldn't test with: 3.0.2-preview (2021.1.0a2 - because of Null Reference errors thrown from the Simulator window)
Note: Removing Input Action Asset from the Player Input component in GameObject "Player Input" will produce expected results
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Fixed in: 2021.1.0a3