Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2017.4.X, 2018.3.X, 2019.1.X
Votes
13
Found in
2017.2
2017.2.0b10
Issue ID
949522
Regression
Yes
"Sub-emitters must be children of the system that spawns them" error is shown even though sub-emitters are correctly parented
How to reproduce:
1. Open "EmitterIssue" project and "test stage 1..." scene
2. Enter playmode and pause it
3. Observe "Sub-emitters must be children of the system that spawns them" error appearing
4. Double click on the error in the console, it highlights "Debris" GameObject that has two sub-emitters "DebrisSmoke" and "DerisFire" that are correctly parented under "Debris" GameObject
Expected result: Error should not be shown, since "DebrisSmoke" and "DerisFire" sub-emitters are correctly parented under "Debris" GameObject as required in 5.6+ versions
Regression introduced in - 2017.2.0b1
Reproducible with - 2017.3.0a7, 2017.2.0b11, 2017.2.0b1
Not reproducible with - 2017.1.0p2, 2017.2.0a4
Note - Deleting some of the "MediumExplosionFX" prefabs, fixes the issue
-
mostlyhuman
Aug 03, 2018 04:11
Problem still exists in Unity 2018.2.1f1, it appears to also cause a nasty memory leak. Again when this happens if you click on one of the parent particle systems in the scene and then go under subemitters and click the linked gameobject in the field it will highlight the child emitters location in the scene hierarchy and you can see it will be under the wrong parent and not the expected parent. So somehow they are being jumbled and assigned the wrong parent, this only happens when they are instantiated through code. If you drag them in as prefabs they maintain their correct relationship.
-
shawnp
Jul 20, 2018 14:02
I am seeing this issue on 2017.3.1.f1 Personal... It started happening today after I opened up my project. No changes had been made, so I can't give you any helpful steps to reproduce it. It doesn't seem to break anything though, just has an error message.
It it highlighting a regular scene object and the sub-emitters are clearly child objects of the system. Hope that helps.
-
Justin-Wasilenko
Jul 12, 2018 12:07
I have this as well in 2018.1.6. Doesn't seem to affect anything. Just displaying a error message.
-
mostlyhuman
Mar 28, 2018 13:31
Update: even though these are being instaniated from a prefab, i have found that when many are spawned the children are actually being assigned to the wrong parent which is triggering the error. once they are all spawned while in play mode, if you look at one of the parent particle systems in the scene and then go under subemitters and click the linked gameobject in the field it will highlight the child emitters location in the scene hierarchy and you can see it will be under the wrong parent and not the expected parent.
-
mostlyhuman
Mar 22, 2018 21:18
I am having this seem issue in 2017.3.1p4, when spawned the sub emitters are correctly parented to the particle system that spawns them yet it produces this error. If I drag the prefab directly into the scene it doesnt produce the error but when it is instantiated it does.
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
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
richardkettlewell
Jan 25, 2019
We are currently testing a fix for this issue.