Search Issue Tracker
Fixed
Fixed in 6000.0.64f1, 6000.2.16f1, 6000.3.1f1, 6000.4.0b1, 6000.5.0a3
Votes
1
Found in
6000.0.61f1
6000.2.10f1
6000.3.0b8
6000.4.0a3
Issue ID
UUM-124857
Regression
Yes
Transparent pixels are still hit when alphaHitTestMinimumThreshold is set to a non-zero value
How to reproduce:
- Open the "IN-121871.zip" project
- Open the "InteractionTestScene" Scene
- Enter Play Mode
- Hover the mouse over the "Character_General" Sprite's head (furthest Sprite) in the Game view
- Observe the Game view
Expected result: The furthest Sprite is highlighted
Actual result: The nearest Sprite is highlighted
Reproducible in: 6000.0.54f1, 6000.0.61f1, 6000.2.10f1, 6000.3.0b8, 6000.4.0a3
Not reproducible in: 6000.0.53f1
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Note: Tested with "alphaHitTestMinimumThreshold" values from 0.1 to 0.95 - all results were the same
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
- [WebGPU] clearing 2d array texture only clears first slice
- Particle System Renderer icon is missing in Animation window > Add Property context menu
- [Android] Legacy, TMP and UI Toolkit Input Field language toggle to some non-latin alphabet languages does not work with external keyboard
- Crash on keywords::LocalKeywordState::operator when calling ShaderUtil.GetPasskeywords with ShaderType.RayTracing set as the third parameter
- Inconsistent “Remove property” behavior when removing child properties in Animator window
Resolution Note (fix version 6000.2.16f1):
The issue has been fixed; however, the 6000.2 stream has reached End of Life as of 6000.2.15f1, and the fix won't be accessible