Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.1p1
Issue ID
1012128
Regression
No
Inaccurate position of image when using Image.alphaHitTestMinimumThreshold
How to reproduce:
1. Open given Unity project
2. Enter "Main" scene
3. Enlarge circle to 400 for a better result
4. Enter Play Mode
5. Hover the mouse button over the white circle
Expected result: The collide between mouse cursor and circle should be more accurate
Actual result: When hovering not over the circle, the mouse cursor is changed sometimes
Reproducible with: 2018.2.0a5, 2018.1.0b11, 2017.3.1p4, 2017.2.2p1, 2017.1.3p2, 5.6.5p3
Note: this bug only happens when the game window is anchored in the main unity window, the mouse y axis origin is slightly lower than the bottom of the window, so the y mouse position is always a few pixels higher than it should be. If you pop the window out of the main window, the bug no longer appears.
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Resolution Note:
low priority and minor or cosmetic issues. likely won't fix.