Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.2.4
Issue ID
1185717
Regression
No
Calling ReleaseAsset() on AssetReferenceSpriteAtlas results in lost reference and unusable SpriteAtlas
How to reproduce:
1. Open attached project "SpriteAtlasReload.zip" and scene "Example"
2. Enter Play mode
3. Click on "Create Sprites" -> "Load Atlas" (UI is visible)
4. Click on "Release Atlas" -> "Load Atlas"
5. Observe the created UI
Expected result: the same UI as in step 3 is visible
Actual result: the UI is white, SpriteAtlas is not found
Reproducible with: 2018.4.10f1, 2019.2.7f2, 2019.3.0b4, 2020.1.0a5(1.2.4)
Could not test with: 2017.4 addressable and other package manager errors
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 verified in 2020.1.0a15
Resolution Note:
Verified in:
Version 2019.3.12f1