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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Fix verified in 2020.1.0a15
Resolution Note:
Verified in:
Version 2019.3.12f1