You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Opening an existing project that has been working since Godot 3 days in latest master floods the log with Moving child node positions inside the SceneTree is only allowed from the main thread. Use call_deferred("move_child",child,index).
Note that these errors are given just opening this scene in the editor. To my knowledge the only place threading is used in this project is that its using the ResourceLoader but this only effects runtime.
Note that at the same time the console within VSCode gets flooded with:
The error not referring to what code leads to this issue means we're looking for a needle in a haystack and with the editor becoming unresponsive, it's a challenge.
My best guess is that this is caused by this project using @tool scripts that hook into the changed signal of a 3D curve which both triggers the CSG polygon that build the track updating, as well as reposition various other elements.
Steps to reproduce
As right now it's impossible to pinpoint the cause of this, the only way to reproduce is to open the effected project.
Well, I'm stumped. After going through a full bisect, the problem has just disappeared. I'm at a loss to explain it.. Even resetting the project back to freshly cloned from GIT..
Tested versions
System information
Windows 11 - Forward+ - NVidea 4070Ti
Issue description
Opening an existing project that has been working since Godot 3 days in latest master floods the log with
Moving child node positions inside the SceneTree is only allowed from the main thread. Use call_deferred("move_child",child,index).
Note that these errors are given just opening this scene in the editor. To my knowledge the only place threading is used in this project is that its using the
ResourceLoader
but this only effects runtime.Note that at the same time the console within VSCode gets flooded with:
The error not referring to what code leads to this issue means we're looking for a needle in a haystack and with the editor becoming unresponsive, it's a challenge.
My best guess is that this is caused by this project using
@tool
scripts that hook into thechanged
signal of a 3D curve which both triggers the CSG polygon that build the track updating, as well as reposition various other elements.Steps to reproduce
As right now it's impossible to pinpoint the cause of this, the only way to reproduce is to open the effected project.
Minimal reproduction project (MRP)
BastiaanOlij/vehicle-demo#15
The text was updated successfully, but these errors were encountered: