Scott Hong
New member
When implementing Animator in the Behavior Designer way, there is a problem that the tree becomes very complicated, so Opsive gave us some references.
However, it seems that Opsive should provide some examples, not a references.
MecWarriors' way has a problem that the speed of NavMeshAgent is applied as the Animator speed. Unity's way behaves very strange when the NavMeshAgent speed is less than 3. A* I couldn't even find out where the example is.
I don't know if Opsive has not aware of this problem and presented it as a reference, or whether it is trying to get rid of it as a reference because there is no solution?
I believe that a clear solution will be the Opsive's example, not a reference.
Please show and confirm that Behavior Designer can be applied to real projects, not just idea products using Behavior Tree.
However, it seems that Opsive should provide some examples, not a references.
MecWarriors' way has a problem that the speed of NavMeshAgent is applied as the Animator speed. Unity's way behaves very strange when the NavMeshAgent speed is less than 3. A* I couldn't even find out where the example is.
I don't know if Opsive has not aware of this problem and presented it as a reference, or whether it is trying to get rid of it as a reference because there is no solution?
I believe that a clear solution will be the Opsive's example, not a reference.
Please show and confirm that Behavior Designer can be applied to real projects, not just idea products using Behavior Tree.