Search Issue Tracker
Fixed
Fixed in 2020.3.43f1, 2021.3.14f1
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment