Search Issue Tracker
Fixed
Fixed in 1.21.19, 2.0.3
Votes
0
Found in [Package]
1.21.17
Issue ID
ADDR-3435
Regression
Yes
Removing a Sprite from a Sprite Atlas causes an Exception in CalculateSceneDependencyData
Reproduction steps:
1. Open the "IN-45683.zip" project
2. Open "Assets/Scenes/SampleScene"
3. Open the Addressables Groups window (Window -> Asset Management -> Addressables -> Groups)
4. Click on Build -> New Build -> Default Build Script in the Addressables Groups window
5. Open "Assets/Scenes/TestAtlas.spriteatlasv2"
6. Add the "test_icon" Sprite to the "Objects for Packing" field in the Inspector window
7. Click on the "Pack Preview" button in the Inspector window
8. Repeat step 4 and observe the Console
Expected result: The build succeeds
Actual result: The build does not succeed
Reproducible with: 1.21.1 (2021.3.28f1, 2022.2.2f1, 2023.1.0b7, 2023.2.0a5), 1.21.14 (2021.3.28f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a21)
Not reproducible with: 1.20.5 (2021.3.28f1, 2022.2.0b12, 2023.1.0a17)
Reproducible on: Windows 10
Note: Reproduction may be inconsistent in some versions, sometimes the issue reproduces after building two times after adding the "test_icon" Sprite
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