Search Issue Tracker
Fixed in 2021.1.X
Planned for 2020.3.X
OnMouseDown is not called when clicking on a GameObject when targeting displays other than "Display 1"
How to reproduce:
1. Open the attached project's Scene labeled "EditorMouseInput"
2. Enter the Play Mode
3. In the Game view, target the "Display 1"
4. Click on the Sphere
4. Inspect the behavior
5. In the Game View, target the "Display 2"
6. Click on the Sphere
7. Inspect the behavior
Expected result: OnMouseDown is called and the Sphere is colored blue
Actual result: OnMouseDown is not called on the Sphere shown on "Display 2"
Reproducible with: 2018.4.32f1, 2019.4.21f1, 2020.2.7f1, 2021.1.14f1, 2021.2.0b2, 2022.0a2
Important: OnMouseDown is called on Sphere shown in "Display 1" when clicking in "Display 2" if the click is relative to the displayed Sphere's position on "Display 1"
- Partially fixed in Unity 2021.1.0a8 and versions above. OnMouseDown is called on "Display 2" but when clicking on a specific point on "Display 2" it can be called on "Display 1" as well.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Camera active Texture is not written if another camera has a Script using "OnRenderImage"
- The Camera's background color is white when the device Appearance is "Light Mode"
- Particle System isn't culled off-screen when the Culling Mode is set to Automatic and the Simulation Space is set to World
- Main Player window is moved to the primary display when it's launched on a 3rd monitor and the 2nd monitor is activated
- Crash on Mesh::RecalculateBounds when assigning not enough vertices for two submeshes