Search Issue Tracker
Fixed in 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.
- UI Builder - Transitions on elements with hover are only applied the first time hover occurs
- Unity drains raw input message queue before Rewired can process each event, making it miss some
- Old input system misses some mouse movement if the new input system is also enabled
- [URP] _ProjectionParams.x with Overlay rendering
- Thumbnails in a Project window get darker after reimporting assets