I noticed that when an enemy is in Patrol state, and then it Dies in the game, the switch to the first branch happens not instantaneously. It takes several frames before the Try In Order switches to the Death branch.
I have read in the docs that Behavior Graph is designed to be performance efficient, but in my case this efficiency causes problems.
It’s strange to see in the game that the bullet has already hit the enemy, but the animation of the death played with delay.
Dear Unity Developers, could you please tell me:
Why this happens? Is it intended?
Is it possible to increase the Update Rate of the Tree?
If not, what workaround would you suggest?
Platform: Windows 10
Behavior Version: 1.0.7
Unity Version: 6000.0.25f1
We’re aware of this issue and are actively working on it. Fundamentally when it comes to a sequence like the Try In Order each child is executed in successive frames. We’re currently working on making the graph do as much as it can each frame rather than spreading it out like it does now.
I tested and it seems like Graph reacts much more quickly than before. Thank you for your work!
But I noticed one possible issue with the code you provided:
Let’s imagine that in the Selector (TryInOrder) we have 2 children that are both Failed. From your code, I see that for Selector it will be still a Success:
protected Status StartChildNodesUntilCompleteOrWaiting(int childIndex)
{
m_CurrentChild = childIndex;
while (true)
{
if (m_CurrentChild >= Children.Count)
{
// HERE WE'LL HAVE SUCCESS EVEN IF CHILDREN WERE FAILED
return Status.Success;
}
var status = StartNode(Children[m_CurrentChild]);
if (status == Status.Failure)
{
// Move on to the next child.
++m_CurrentChild;
continue;
}
if (status == Status.Running)
{
return Status.Waiting;
}
return status;
}
}
Now, imagine that this Selector is within another Selector. The outer Selector will not check for other children because the inner Selector always returns Success.
Could you please tell me, do you see this as an issue?
Hey, you’re right! I’ll make sure I correct this for the release
The correct way would be to just return failure there, as we would’ve returned success if a child succeeded so you should be able to safely change that
@ShaneeNishry , thank you very much for such a quick reply!
This:
if (m_CurrentChild >= Children.Count)
{
return Status.Failure;
}
in the SelectorComposite.cs works well for me. I checked the same method for SequenceComposite.cs - the return of the Success seems correct there.
I am glad you guys directly work like that with the community. I respect that very much!
I’ll mark your reply with the attached scripts as a solution. I wish you a very good day and evening!
(and if possible, could you please ask someone to check my recent bug report - Changes made in Subgraphs are not perceived by the Main Graph - the bug is very annoying)
