Closed engimaxp closed 8 months ago
reproduced in 4.1.3stable
Thank you for reporting this! I've made a fix and at least in my initial tests it seems to be working correctly. I had the same issue with the Visibility sensors as well, so the impact was greater than just the Area2DSearchSpace.
it may not be a problem, there is a work around now if you put area2d under the ai node ,when the node is queued free ,godot first queue free the area2d node ,then the utilityai node the utilityai node deconstruct method will try to disconnect area2d signals and fail to fix this ,try put the area2d node above the utilityai node, then it will work smoothly
great work bro