This is indeed a bug. It is actually a by-product bug of a bigger issue in how SubTrees are handled and which is meant to be fixed for the next version. The problem is that BehaviourTree SubTrees, (in contrary to all other type of nested graphs), are not handled in the same way for (negligible) performance reasons, but that inconsistency can be the source of bugs like this. As such, I aim in the next version for SubTrees to be handled in the same manner and thus have such (as this) bugs resolved altogether.
If your current workaround does not work for your until the next version update, I can rush up the fix and send it to you if you want.
Just let me know if so and thank you for the bug report!
Join us on Discord: https://discord.gg/97q2Rjh
Login
Register
By registering on this website you agree to our Privacy Policy.