Here’s a screenshot of what I mean:
The root node of the behavior tree is the only one running. Is there a specific reason for this? This same behavior tree sequence worked in 4.6, so I’m wondering if anything changed in 4.7 to have caused it…
1 Like
The only thing that crosses my mind is that all the tasks fail and BT is unable to “stay” in any task. I’ve also noticed that one of your “leaf” selectors doesn’t have any child tasks - I wonder if that’s messing up the BT code… Regardless, could you record a vis log and send it our way (or investigate it on your own - who knows, you might find something interesting! :))
(to summon vislog UI just run console command vislog, or look around in the menus - I think it’s somewhere there :D)
Cheers,
–mieszko
I have the same issue, no idea whats causing it. Followed the AI tutorial on the unreal docs to get some basic ai in and it wont run just stay at the Root node.
The reason for this behavior is behavior tree component not being able to find a task it can run. Try adding a “fallback” wait task and you’ll notice that one gets run. I suggest using visual logger for debugging this issue.
Alright thanks for the help 
Hey! I’m having this same issue, but I’m just trying to get my AI Character to follow me. I did the vislog thing and Found some things that were questionable but don’t know how to fix them…
Any help would be greatly appreciated!!!
My problem was in the AgroCheck blueprint that i copied from the tutorial, the Get All Actors of Class node had no class set
Hope this helps someone!
Ran into this problem myself in version 4.16.1, I’m finally learning how to pop some AI into my concept project and opted to start with the basic tutorial. This was one of the few posts I found where someone ran into the same problem I did, though it seems like it was kind of left without any resolutions. Here’s what I figured out for my situation:
-
Set the “Get All Actors of Class” node to have the same class as the object using the AI (since this will be used in the Actors to Ignore pin for the Multisphere Trace).
-
Make sure the multisphere trace radius is set to a value greater than 0.0 (I didn’t spot that it was set to 1500.0 in the node picture, so my AI was scanning a radius of nothing).
-
The “Line Trace by Channel” node must have the trace channel as “Camera” rather than “Visibility” or else the object that it’s checking for just comes back as “None.”
Using the Visual Logger, breakpoints, and also just setting variables to output their values to the log during play helped me stumble through this one, so those are my recommendations for anyone who has different problems getting that tutorial up and running.
Thx for saving me hours of searching for the problem. I looked over the “Camera” rather than “Visibility” part so that was my problem.
So I thought I would let people know what the solution was that I found. It was incredibly easy to miss and i rewent through the entire thing twice.
After hours of going through and break pointing everything. The output log was giving warning, invalid object type. I found out my DesiredObjectTypes in the agrocheck wasn’t set. I didn’t see this little bit in the instructions, but there needs to be a variable added to that of type pawn. I compiled it, and the ai ran at me and scared me. Hope this helps anyone struggling like I did.
I dont see any error in the visual logger
Before every thing else try that.
When you switch between trees, sometime there is a wrong timer or tick call cause there is 0.1 sec or more, specialy if you set some values on a BTS that you need for this tree, so tick “Restart timer” and “Call tick at start” to prevent the issue.
That solve the problem for me 