Search Issue Tracker
Fixed in Unity 5.4.0
[Shuriken] ParticleSystem added via AddComponent uses pink error shader and different default values in stand-alone
ParticleSystem added via gameObject.AddComponent<ParticleSystem>(); displays pink error shader in stand-alone player. They also don't inherit the default settings (maxParticles, startLifetime, etc.)
1. Open AddComponent scene from attached project
2. Press play and observe usual particle system behavior.
3. Build stand-alone player and launch it.
4. Observe particle system shoots only 1 particle and it's using the error shader.
Expected outcome: particles in stand-alone player to display as they do in editor and to use the same default shader.
- Issue is present in 5.3.1f1
- Looks like many (all?) variables are set to 0 / null in stand-alone player.
- As a workaround, user has to manually set all particle properties (material, size, count, etc.)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Absolute paths from included packages cannot be converted to virtual paths in Assets/Packages
- Crash in VCProvider when upgrading project from 18.3 to 19.1 and 19.2
- Android Vulkan corrupted rendering when there is no camera in the scene
- Creating mesh assets produces broken blendshapes
- Sort Order is not respected for a newly created Canvas until Play Mode is entered or any adjustments are made