Search Issue Tracker
Fixed in 2021.3.14f1
Fixed in 2020.3.X, 2020.3.43f1, 2021.3.X
Votes
3
Found in
2020.3.34f1
Issue ID
UUM-2221
Regression
Yes
[Backport] Animated Image property Raycast Target does not function when disabled before entering Play Mode
Reproduction steps:
1. Open the attached "RaycastTarget.zip" project
2. Enter Play Mode
3. In Game view, interact with the Button through the overlapping Image
Expected result: The Button region below the Image is not interactable when the Image Raycast Target is enabled (for visual representation Image becomes opaque)
Actual result: All regions of the Button are always interactable
Reproducible with: 2020.2.0a7, 2020.3.13f1, 2021.1.13f1, 2021.2.0b1
Not reproducible with: 2018.4.36f1, 2019.4.28f1, 2020.2.0a5
Note:
- Having Raycast Target (property of Image) enabled before entering Play Mode fixes the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment