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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note:
Fix verified in 2020.1.0a15
Resolution Note:
Verified in:
Version 2019.3.12f1