AI behaviourTree problem since 4.13

Mamouf · September 5, 2016, 9:08pm

Hi,

Since the new Version my BehaviourTree is not working properly.
The AI should Petrol between 4 Waypoints and it works fine before the new Version.
When the Ai reaches the second Waypoint my TargetActor is going to be Set, but i´m not setting it in any way.
Because of that, the AI stops and is not moving to the next Point.

Sean_L · September 6, 2016, 3:54pm

Hello,

Could you provide a simplified test project so I can take a closer look at your setup? I’ve tested this on my end, but there are quite a few variables that could be different between our setups so I’d like to see what you have.

Mamouf · September 6, 2016, 10:17pm

Ok, that should be it.

Thanks

Sean_L · September 12, 2016, 5:25pm

Unfortunately, we can only accept files from Dropbox and Google Drive. Could you please upload it to one of those services and provide an updated link?

Thank you

Mamouf · September 13, 2016, 9:05am

than google drive.
Hope that works.

Sean_L · September 13, 2016, 6:49pm

After taking a look at your setup, this doesn’t appear to be a bug. I notice that the issue is that your Target Actor is getting set to Waypoint 2. I recommend taking a closer look at your setup to determine how your actor is being set to the Waypoint, and also change Target Actor so it can only accept a reference to your player (assuming that’s what you’d like it to accept). If after taking a few minutes to attempt to debug the issue, you still believe it to be a bug, feel free to provide further information and I’ll be glad to take another look.

Have a great day!

Mamouf · September 26, 2016, 11:33am

Thanks for your answer.
I took a closer look at my setup but i´m not setting the TargetActor in any way.
The BaseClass KeyType of the TargteActor Key in my Blackboard is set to character but its still setting the Waypoint 2 (which is definitely not a character).
It really doesn´t make sense to me.
Could you please take another look and show me what i´ve overlooked.
Thanks in advance

Sean_L · September 27, 2016, 6:57pm

After further investigation, I’ve noticed you’re using a selector for your Target Actor is Set Condition. Replace this with a sequence and then add the Blackboard Based Condition to it to see if TargetActor is Set. This should resolve the issue.

You’ll also need to create a new BT Task to clear the value of the TargetActor, as you never do this and it causes it to always be set to Waypoint2 once it is initially set.

Here’s what mine looked like:

Doing both of these things will get it working again.

Have a great day!