Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f3
Issue ID
1006400
Regression
No
Size of Terrain in built Asset Bundle file is larger than Terrain asset file itself
How to reproduce:
1. Open the user attached project
2. Go to "Builds" --> "Build Asset Bundles" (custom menu items, to build asset bundles)
3. Compare built Asset Bundle size and Terrain asset file size
Result: AssetBundle size is around ~100kb bigger than Terrain asset file
Reproducible with - 2018.2.0a1, 2018.1.0b9, 2017.3.1p2, 2017.3.0a1
Note - Both Standalone and Android as Asset Bundle build targets produce similar results
By design --> So the Terrain Asset in the Assets folder contains the TerrainData (hight map data) and the splat map (texture painting data) and references to things this terrain needs such as textures, materials, and shaders. Building this asset into an asset bundle causes all of the dependencies to be pulled into that bundle. This includes the textures used to paint the terrain, all the shaders needed, and materials. This causes the final size of the terrain to appear much larger because you are looking at the full set of dependencies, not just the minimum data needed.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment