Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.2.17f1
2020.1
Issue ID
1217454
Regression
No
Assigning a referenced asset to a Asset Bundle instead of leaving it as automatic increases the Bundle size
How to reproduce:
1. Open the attached project
2. Make sure the "project/bundles" folder is empty
3. Tests > Build Bundles
4. Check the bundle sizes in "project/bundles"
Actual result: The "chest 1" (Where the referenced asset is added to bundle) bundle takes more space then "chest 2" (bundle where the asset is just referenced)
Expected result: The bundle sizes doesn't differ.
Reproducible with: 2018.4.18f1, 2019.2.20f1, 2019.3.3f1, 2020.1.0a25, 2020.2.0a1.
Notes:
- In user's full project the size increases are a lot higher.
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] The warning "Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak" is displayed when ShaderVariantCollection.WarmUp is called
- RectangleContainsScreenPoint returns false for some points even when the points are in the rectangle
- [iOS] Stacked camera does not render when using post effects
- TextField cannot be edited in an extended Editor window when double-clicking it
- [VisionOS] visionos build do not add plugin or frameworks
Resolution Note:
Assigning an asset to an explicit bundle tells the build system the entire asset should be available at runtime. Where pulling in the asset via reference pulls in only the used components of that asset. This is by design.