Search Issue Tracker
By Design
Votes
0
Found in
2020.3
2020.3.25f1
2021.2
2022.1
2022.2
Issue ID
1395511
Regression
No
Warnings are logged when entering Play Mode if Particle System is using "Sub Emitter" and having Particles System as a child
How to reproduce:
1. Open the user attached project
2. Enter Play Mode
3. Observe the Console window
Expected result: No warnings
Actual result: "Sub-emitters may not use stop actions. The Stop action will not be executed." warnings appear
Reproducible with: 2020.3.31f1, 2021.2.16f1, 2022.1.0b12, 2022.2.0b8
Coult not test with: 2019.4.36f1 (Errors after downgrade)
Note: Not reproducible if disabling child object (Particle System)
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
- [Scene View][Ubuntu] Prefab mode UI ghosting in HDRP
- Deleting AudioMixer asset throws MissingReferenceException and breaks the Audio Mixer window
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
Resolution Note:
The problem is not that you've called Stop (which, as you say, you haven't, and didn't even know existed)
A reminder of the message we are seeing:
"Sub-emitters may not use stop actions. The Stop action will not be executed."
The problem is that you have set a Stop Action on a Sub-Emitter. The message is telling you that this is not allowed.
Clicking on the message highlights the systems at fault. They are called "Crackle" and "Flash". They are sub-emitters of "detonationCrackles" and use the Destroy Stop Action.
Setting Destroy on the parent system is sufficient (which you already have done) it should destroy itself and all its sub-emitters when it's finished.
So just set the Stop Action on those Sub-Emitters back to None and you should be good to go!