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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Resolution Note:
Fix verified in 2020.1.0a15
Resolution Note:
Verified in:
Version 2019.3.12f1