Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.4
2019.4.17f1
2020.3
2021.2
2022.1
Issue ID
1396119
Regression
No
[Serialization] Mesh shape in particle component prefab will remain in build when object in Scene has no mesh shape
How to reproduce:
1. Download the attached project 'ReferenceTest.zip'
2. Build and Run 'SampleScene' Scene with Development mode selected
3. Open Profiler and connect it to the built app
4. In Profiler select Memory module and select 'Simple' view in the module details panel
5. Observe 'Meshes' stats under 'Object stats' in the module details panel
Expected result: The app is using 0 meshes
Actual result: The app is using 1 mesh with ~66 kb memory usage
Reproducible with: 2019.4.34f1, 2020.3.26f1, 2021.2.8f1, 2022.1.0a16, 2022.1.0b4
Not reproducible with: 2022.2.0a1, 2022.2.0a2
Notes:
- The issue can be reproduced on standalone and mobile builds
- The issue can't be reproduced on Editor
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a1