Search Issue Tracker
Fixed in 1.19.1
Votes
0
Found in [Package]
2019.4
2019.4.13f1
2021.1
Issue ID
1289151
Regression
Yes
All Dependent AssetBundles are changed when modifying a SpriteAtlas in Shared AssetBundles
How to reproduce:
1. Open the attached project
2. In the top toolbar, select Bug Report->Execute
3. Inspect the Console Window
Expected result: All AssetBundle build scenarios are run successfully
Actual result: Modifying a SpriteAtlas in Shared AssetBundles causes changes to all Dependent AssetBundles
Reproducible with: 2019.4.14f1, 2020.1.13f1, 2020.2.0b11, 2021.1.0a5
Not reproducible with: 2018.4.29f1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 1.19.1):
Scriptable Build Pipeline now has a build option called Non-Recursive Dependencies. Since the Texture is a direct dependency of the Sprite Atlas v1, this will ensure that only the bundle in which the Sprite Atlas v1 is assigned to will have a reference to the generated Texture. If the Sprite Atlas v1 is not assigned to a bundle itself, then the existing behavior will persist.