Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2019.4
2020.3
2020.3.4f1
2021.1
2021.2
Issue ID
1335900
Regression
No
Atlas Cache is inconsistent after disabling Sprite Packer and deleting atlases outside Unity Editor
How to reproduce:
1. Open the user's attached project
2. Build and Run the project (observe that left-side image can't be loaded)
3. Close the Build and the Unity Editor
4. Delete Assets/TestAtlas
5. Open ProjectSettings/EditorSettings.asset with the text editor and modify the line "m_SpritePackerMode: 4" to "m_SpritePackerMode: 0"
6. Open the project again
7. Build and Run the project and observe the image on the left side
Expected result: sprite is correctly rendered
Actual result: sprite is white meaning that it cannot be loaded (although the sprite isn't used in any atlas anymore)
Reproducible with: 2019.4.26f1, 2020.3.10f1, 2021.1.8f1, 2021.2.0a17
Could not test with: 2018.4.35f1 (could not downgrade)
Note: Sprite is loaded correctly after deleting "Library/AtlasCache" and "Library/SpriteAtlasDatabase.asset"
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2022.1):
A fix for this issue will be available on Unity 2022.1.0a2 and above