Search Issue Tracker
Fixed
Fixed in 2022.3.63f1, 6000.0.48f1, 6000.1.1f1, 6000.2.0a7
Votes
1
Found in
2021.3.46f1
2022.3.54f1
6000.0.30f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-90488
Regression
No
UI Source Image property gets set to 'None' when using a specific Sprite and Play mode is entered
Reproduction steps:
1. Open the attached “Unity 6 HDRP.zip” project
2. Open the “test sprite” Scene (Assets > #)
3. Select the ‘Image' GameObject from the Hierarchy (Canvas > Image)
4. Observe the ‘Source Image’ property in the Inspector
5. Enter the Play mode
6. Observe the ‘Source Image’ property in the Inspector again
Expected result: The “0005_Character 1” Sprite is still referenced in the ‘Source Image’ property
Actual result: The ‘Source Image’ property is set to None
Reproducible with: 2021.3.46f1, 2022.3.54f1, 6000.0.30f1, 6000.1.0a7
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Does not reproduce in the Player
- Could only reproduce with the “0005_Character 1” Sprite
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Resolution Note (fix version 6000.2.0a7):
Fix for this issue is available on Unity 6000.2.0a7 and above
Resolution Note (fix version 6000.1.1f1):
Fix for this issue is available on Unity 6000.1.1f1 and above
Resolution Note (fix version 6000.0.48f1):
Fix for this issue is available on Unity 6000.0.48f1 and above
Resolution Note (fix version 2022.3.63f1):
Fix for this issue is available on Unity 2022.3.63f1 and above