Search Issue Tracker
Fixed
Fixed in 7.0.12
Votes
2
Found in [Package]
7.0.11
Issue ID
DANB-515
Regression
Yes
Sprite Resolver's "SetCategoryAndLabel" method doesn't take effect
Reproduction steps:
1. Open the attached “Repro” project
2. Open the “Assets/DemoScene.unity” Scene
3. Enter the Play Mode
4. Press the “Play” Button in the Game View
5. Press on the left side of the screen to move the camera to the left
6. Press the purple button above the tower on the left 5 times
7. Press on the left side of the screen to move the camera to the left
8. Select the “Tower3” GameObject (LeftSceneSide > MapScene(Clone) > Castle > CastleParts > lv2_1) in the Hierarchy window
9. Observe the “Label” field under the Sprite Resolver Component in the Inspector window
10. Observe the Console window
Expected result: The Console logs “Entry label it has” entry, but the Sprite Resolver reports “Entry_1” and the Sprite selected is incorrect
Actual result: The Console log and the Sprite Resolver’s Label field match, the Sprite selected is correct
Reproducible with: 7.0.11 (2021.3.30f1)
Not reproducible with: 8.0.5 (2022.1.241f1), 9.0.3 (2022.3.10f1), 10.0.3 (2023.1.14f1, 2023.2.0b9, 2023.3.0a5)
Fixed in: 8.0.0-pre.3 (2022.1.0b1),
Reproducible on: Windows 10 Pro (22H2)
Not reproducible on: No other environment tested
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
- 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
Resolution Note (fix version 7.0.12):
Apologies for the delay in the update, this has been fixed for 2D Animation 7.0.12