Changing behaviour Tree doesn't call abort on current task

anonymous_user_435a64b01 · January 19, 2015, 10:16pm

Changing current behaviour tree doesn’t cause current task to call its ReceiveAbort function. It means a task keeps running until completion when a behaviour tree is stopped. This causes problems when I want an enemy to stop all attacks while stunned and it keeps executing its last attack. And then being stunned.

Is this intended behaviour?.It feels wrong.

I can’t seem to work out when ReceiveAbort is ever supposed to be called either.

I fixed this by making AbortCurrentTask() in BehaviourTreeComponent public and adding a StopBehaviourTree function in AIController.cpp that calls this then StopTree() on current behaviour tree. But I’d rather not be running a custom version of UE4.

IceWraith · February 12, 2015, 12:37pm

Thanks for reporing this issue.

Fix is already on way. Your workaround should be safe to use, unless you have tasks that can delay their abort.

anonymous_user_435a64b01 · February 12, 2015, 1:48pm

Glorious! Might this be included in 4.7 release?

IceWraith · February 12, 2015, 1:51pm

No, it was found too late

IceWraith · February 12, 2015, 2:01pm

Yes, workaround have to stay until 4.8.

anonymous_user_435a64b01 · February 12, 2015, 1:56pm

: (

Sneak it in! It will be our secret…

In all seriousness, thanks anyway and mark this one answered I guess. We’ll use our workaround until, I assume, 4.8?

anon26705860 · February 12, 2015, 6:51pm

You haven’t fixed this in master yet correct?

anonymous_user_33800a51 · March 19, 2015, 3:15pm

Hi dzeligman,

Yes, this should be in Master. It was committed on 2/16 as CL#2446753.