Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.4.0b3
Issue ID
764899
Regression
No
[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.)
Repro steps:
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.
Notes:
- 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.
Latest issues
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Add comment