(4.26)
I seem to be having an issue in my behavior tree. If i leave it back to how it was before i changed it from receive tick, everything works as it should but there’s a lot of ticks that i don’t want or need. If i change the receive tick to receive search start instead, it half way works but its getting stuck where my AI chooses its walk to location and then walks to it, then waits for 9 seconds, THEN it finally detects that its attacktarget has been set so do the other side of logic. This is wrong though as it should immediately detect the ai has an attack target and abort out of the moveing/wait 9 secs and now go through the logic again so it then has an attack target set and do its other side of tree.
Hopefully that makes sense.
Im using receive search start for the first time to improve my behavior tree for better optimization. Imagine having 50 AI on screen spamming through loads of ticks and thats just for 1 player. 10 players fighting across the map? not good lol. I was noticing fps drops when fighting an AI and i start moving around and they give chase, instant loss of 5-10 fps, i stop moving and the ai settle in on me and the fps comes back. I tracked it down to too many ticks as the culprit.
Here are some screenshots of the code itself. I have tried every single mix/match of the settings for these tasks so they abort both on result change or value change for attack target notset, etc but nothing changes. The only thing i can think of is either things work differently with the receive search start, so maybe i need some sort of new logic? I’m clueless here haha. Any help would be greatly appreciated!
video:
