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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Fix verified in 2020.1.0a15
Resolution Note:
Verified in:
Version 2019.3.12f1