Topic was automatically imported from the old Question2Answer platform.
Asked By
Dieter
Hey all,
I’m not sure if this is a bug or I’m just doing something funky. I’m getting the error:
Parent node is busy setting up children, add_node() failed. Consider using call_deferred("add_child", child) instead.
Now I did figure out you’re not supposed to use add_child inside _ready so I’ve refactored until all my _ready()s are clean and use call_deferred if adding nodes. However, I still get the error. I have a couple of more issues with it:
It does not point to any specific line in my code. This makes it very hard to debug.
It seems to run before my actual code is run. See below for a copy paste from my debugger. It shows right after – Debugging process started –
It also keeps appearing after I close the game down.
Does anyone know what’s going on and how to solve this? Many thanks!
--- Debugging process started ---
Parent node is busy setting up children, add_node() failed. Consider using call_deferred("add_child", child) instead.
Godot Engine v3.5.stable.official.991bb6ac7 - https://godotengine.org
OpenGL ES 2.0 Renderer: Apple M1
Finally I found the cause of the error. Just posting it here in case it helps someone else. It was a sprite that was being loaded and set in the ready() function an obscure effect scene. So apparently load() in _ready() also causes the “Parent node is busy setting up children, add_node() failed. Consider using call_deferred(“add_child”, child) instead.” error.
A couple of things I thought are not-helpful:
The error message does not mention load(), just add_child.
The error message does not point to the line or even script where the error is happening.
The error message happens strangely before and after the debugging starts/ends.
I had the same issue and in my case was a “RESET” Animation into my AnimatorPlayer:
I deleted it and now I don’t see the warning.
Disclaimer: I am very new to Godot
Thanks, this fixed it for me too, this was driving me crazy. It also caused knock-on effects on the rect_position of the node where when I switched between scenes in the Godot editor, it changed that node’s position to incorrect values.
This error message started to show up for me in Godot 4.3 development version (I’m not sure if it started in dev3 or dev4). In my case I have a tilemap with “object tiles” which were particles. When freeing up the scene (queue_free), it seems the particles were triggering these errors somehow… after removing the “particle tiles” the error went away.
Maybe it is too specific for my case, but just in case it helps someone.
