Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2020.3.23f1
2021.2
2022.1
2022.2
Issue ID
1382782
Regression
No
Built Asset Bundles yield identical file sizes of different Assets when using Standard Build Pipeline
How to reproduce:
1. Open the user attached "AssetBundleBuildTest.zip" project
2. Select the "texture.jpg" file found in the Assets/Texture folder in the Project window
3. Set the Texture Type to "Sprite (2D and UI)" in the Inspector window
4. Build the Asset (BuildAssetBundle -> StandardBuildPipeline)
5. Open the "AssetBundles' folder in the project folder
Expected result: Different Asset sizes
Actual result: Identical Asset sizes
Reproducible with: 2019.4.36f1, 2020.3.28f1, 2021.2.11f1, 2022.1.0b7, 2022.2.0a4
Note: Building the Asset with "ScriptableBuildPipeline" yields the expected result
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
- Label is not centered when using flex-direction: row
- Incorrect initial target position when the Skinning Editor's "Depth" parameter is adjusted on a bone which is set as the "Effector" parameter on the "Limb Solver 2D" Component
- The order of activation for Water Deformers and Foam Generators will cause water artefacts in the Player
- Crash on `anonymous namespace'::PrepareTreesAndWriteWindParamsJobData::Execute when entering Play mode on a specific project
- [Linux] Crash on 'PPtr<RuntimeAnimatorController>::operator RuntimeAnimatorController*() const' when saving a new animation file
Resolution Note:
The size being similar is caused by the texture being included in both AssetBundles with the builtin build pipeline. You can observe the content by using WebExtract on the AssetBundles and Binary2Text on the files. To better understand this duplication you can refer to this section "Duplicated information across AssetBundles" in https://docs.unity3d.com/Manual/AssetBundles-Dependencies.html. ScriptableBuildPipeline will attempt to resolve this automatically. If you run the generated bundles through binary2text you will observe that the prefab one generated by ScriptableBuildPipeline it contains an external reference to the other bundle .