Search Issue Tracker
Fixed
Fixed in 2021.3.31f1, 2022.3.11f1, 2023.1.15f1, 2023.2.0b11, 2023.3.0a6, 7000.0.0a1
Votes
0
Found in
2021.3.29f1
2022.3.6f1
2023.1.6f1
2023.2.0b2
Issue ID
UUM-44474
Regression
No
OnMouseDown is not called after the Player window is resized with Display.SetParams when multiple displays are used
Reproduction steps:
1. Open the attached project “NoClick”
2. Build and run (File > Build And Run)
3. In the Player click on the button in the middle and wait a few seconds (the window will be resized)
4. When the Player window is resized, click on the button again
Expected result: The counter on the button increases after each click
Actual result: The button doesn’t register any clicks
Reproducible with: 2021.3.29f1, 2022.3.6f1, 2023.1.6f1, 2023.2.0b2
Reproducible on: Windows 11
Not reproducible on: Intel macOS 13.4.1 (c)
Note: At least two screens are needed to reproduce the issue
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
- Crash on PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
Resolution Note (fix version 2023.3.0a6):
Fixed in 2023.3.0a6
Resolution Note (fix version 2023.2.0b11):
Fixed in 2023.2.0b11
Resolution Note (fix version 2023.1.15f1):
Fixed in 2023.1.15f1
Resolution Note (fix version 2022.3.11f1):
Fixed in 2022.3.11f1
Resolution Note (fix version 2021.3.31f1):
Fixed in 2021.3.31f1