Search Issue Tracker
Fixed in 7.0.0 pre-2
Fixed in 6.0.4
Votes
0
Found in [Package]
6.0.0 pre-2
Issue ID
1321069
Regression
No
[2D][Animation] Sprite Resolver component not updated when new categories/labels are added into Sprite Library asset
[2D][Animation] Sprite Resolver component not updated when new categories/labels are added into Sprite Library asset (e.g. added a new category).
Repro steps:
1. Created a Sprite Library Asset and added a new category called "head" and populated with different variations.
2. Added a Sprite Library and Sprite Resolver component to my GameObject.
3. Opened up my Sprite Library Asset again. This time to add more categories e.g. "body" and again populated with different variations.
4. Went back to my GameObject and realised that my Sprite Resolver component didn't refresh. The dropdown only still showed "head" and I was expecting to see the newly added category "body" too.
5. Had to remove both the Sprite Library and Sprite Resolver component and re-added them to my GameObject in order to see my new categories with "head" and "body".
Expected result: Sprite Resolver component didn't refresh after updating Sprite Library asset
Actual result: Sprite Resolver component refreshes after updating Sprite Library asset
-
tonytopper
Sep 11, 2023 18:01
Looks like this has regressed.
I am getting this issue in 2D Animation 9.0.3 in Unity 2022.3.7f1. Adding a new label to an existing category in this case. Another complexity is these components are part of a Prefab.
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
- Sprite Atlas remains loaded in memory after scene change or unloading assets
- Decompressing a DeflateStream under IL2CPP misses a few bytes
- Referred style sheet stays dirty after saving when using the UIBuilder
- The Height map Amplitude is not working when using HDRP/LayeredLit
- Infinite inertial tensor rotation values are not discarded (both AB and RB)
Resolution Note (fix version 7.0.0 pre-2):
A fix for this issue is available in 2D Animation package 7.0.0 pre-2 and above on Unity 2022.1.0a2 and above