Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
1
Found in
2018.4
2019.4
2019.4.2f1
2020.1
2020.2
Issue ID
1261459
Regression
No
ParticleSystem.MainModule.stopAction does not wait till particles of the GameObject's child stop emitting before destroying
How to reproduce:
1. Open the attached project "case_1261459-ParticleSystem"
2. Open the Scene "SampleScene"
3. Enter the Play Mode
4. Press Space
5. Observe the results in the Game window
Expected results: the particles of the children stop emitting and then the GameObject and its children are destroyed
Actual results: the GameObject and its children are instantly destroyed even though the particles of the children do not stop emitting
Reproducible with: 2018.4.25f1, 2019.3.16f1, 2019.4.3f1, 2020.1.0b15, 2020.2.0a17
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
- 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
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b2
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.6f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.16f1