Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2019.1.0a11
2019.1.0f2
2019.2.0a1
2019.3.0a1
Issue ID
1150263
Regression
Yes
Mesh of the Particle Mesh Emitter could not be set during runtime in builds
How to reproduce:
1. Open attached project "UnityBugMeshParticleEmitter.zip"
2. Build PC, Mac & Linux Standalone build
3. Open the build
4. Press spacebar a couple of times
Expected result: Particles spawn in all kinds of shapes
Actual result: Particles only spawn in a single point in space or a circle
Reproducible with - 2017.4.27f1, 2019.1.2f1, 2019.2.0b2, 2019.3.0a2
Not reproducible with - 2018.3.14f1, 2018.4.0f1, 2019.1.0a10
Reproducible on platforms: Windows, Android
Other platforms are not tested
Notes:
If there is a particle system in the scene with emission mesh set to a particular mesh, it is possible to set emission mesh of another particle system to that particular mesh during runtime without any issues
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
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
Resolution Note:
After investigating this, it appears to be correct that the mesh doesn't work in a standalone build, because it does not have Read/Write enabled.
Usually, our build process can detect meshes being used by particles, and ensure that the vertices are preserved, but in this case, the mesh is assigned by a script rather than via the Inspector, and we have no way of knowing about this at build time.