Mass Behavior State Tree bug?

Development Programming & Scripting AI
,
1

Hello, Im working with Mass AI and State Trees. I think I have found a bug.
My state tree is using Enter Conditions for tasks and it appears a child task with a boolean compare is affecting a boolean compare in a task that is 2 nodes up in the parent chain.
If I remove the bool with the red arrow, the State tree claims the smart object.
If I check the box and make the bool on the child task True, then the state tree claims the smart object.
If I uncheck it and make it False, the state tree no longer claims the smart object.
Is this a bug or am I doing this wrong?

image
image808×672 63.6 KB

Like this, it does NOT claim the smart object

image
image519×269 12.1 KB

Like this, it DOES claim it, even tho that second bool shouldnt get evaluated unless it can claim the smart object.

image
image489×262 12.1 KB

2

Running into a similar issue. Kind of surprised this is not mentioned elsewhere

3

Can you share a Visual Logger on Rewind Debugger screenshot of how the evaluation in this issue is being done? I have a feeling that the StateTree is attempting to enter the CatchBall state since it is the leaf state. The system won’t attempt to claim a Smart Object in Claim until the states are fully entered, and if one state fails the enter condition, the transition fails without starting the task on other states.

What happens if you set the Claim state to use the Try Enter behavior and then trigger a MassSignal for the tree once the SO is successfully claimed to go to the next state.

-James