Search Issue Tracker
Fixed in 2017.4.X
Votes
0
Found in
2018.2.0b1
Issue ID
1027837
Regression
Yes
Mouse events aren't called in a build when the view is rendered by a camera which isn't last in draw order
Repro:
1. Open QA attached project "repro"
2. Enter Play Mode
3. Click and hover the mouse over both cubes
4. Exit Play Mode
5. Build and run the game: File -> Build and Run
6. Repeat step 3 and observe
Expected: each Cube gets rotated and its color changed when hovering and clicking on it both in Play Mode and in the build
Actual: the Cube on the left neither gets rotated nor changes its color when hovering and clicking on it in the build
Reproducible with: 2018.2.a6, 2018.2.0b1
Not reproducible with: 2017.1.3p3, 2017.2.2p3, 2017.4.1f1, 2018.1.0f1
Notes: Only the view rendered by a camera which has the highest depth triggers mouse events. This goes for all of the OnMouse events: OnMouseDown, OnMouseDrag, OnMouseEnter, OnMouseExit, OnMouseOver, OnMouseUp, OnMouseUpAsButton.
Fixed in: 2018.3.0a9
Backported to: 2017.4.11f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment