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
- Post Processing SMAA breaks when HDR mode R11G11B10 is selected and Color Space is changed
- The "UnityWebRequest.result" of the "UnityWebRequestTexture.GetTexture" method changes when accessing "UnityWebRequest.downloadHandler" texture
- Slider rounding does not allow setting certain valid numbers as Values when Low and High Values not set to default
- UI Builder Canvas has too big resizing zone on the outside of the canvas
- GetCurrentAnimatorClipInfoCount() and GetNextAnimatorClipInfoCount() return 0 when animator is in transition
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.