I detach the pawn from the AIController, delete the pawn, spawn a new pawn and attach the new pawn to the old AIController. And now the behavior tree stops to run, or at least I stop seeing “TickUpdateBuilding” in the log. In 4.7 it worked without any problems.
If you have a workaround for this until it is fixed (I really hope for a 4.8 hotfix), please let me know. This changing of the pawn while the controller stays the same is the core element of my whole AI, at the moment it’s doing nothing, so the whole game is not working.
Thanks for the answer, but why did you change this? It’s making my whole AI not work… Did anyone had problems with the way it was before 4.8? If I would want to make the controller reset everything I could just destroy the AI with controller and respawn the AI with a new controller… So before 4.8 I could achieve both behavior, and now I can’t and you say this is by design?
I tried to override the function but I can’t find it in the override menu:
Only OnPosess, but not UnPosess. My project is blueprint only, I can’t do anything in c++.
The important thing for my AI is that the behavior tree is not changing it’s execution, so if it runs a certain task before the pawn changed it has to run the same task after the pawn changed, and most importantly all the blackboard variables need to be 100% the same as before. If I just call RunBehaviorTree on the new pawn this is not the case, right?
I have also tried to not call unposses at all but only possess the new pawn and then destroy the old pawn, but this does not fix it, the behavior tree still stops running.
The reason it has been changed is that it was causing dead AI to have active brains.
It seems there’s currently no way of doing exactly what you need via Blueprints. I can make a quick C++ fix for you if you were willing to compile your binaries from UE4 sources on github.
However, maybe you don’t need that at all. What’s the use case for needing BT to continuously run while you switch the controlled pawn? I mean, we can’t really support it out of the box in a generic case. For example, this would break the behavior if you switched pawns while currently controlled pawn was performing a Move task. Due to the implementation details it could recover, but “new” pawn would not get a new behavior until the previous one finished the move.
I have no problem with compiling from github, but the problem with such a fix is that it will only work for the current version, right? After 4.8.1 is out it would no longer work and I would have to either use the old 4.8.0 with the fix or 4.8.1 without the fix.
I have written you a detailed explanation on how my AI works in a PM in the forums.
No fixes are made specifically for UE4 sub-versions, the fixes are always done on the master branch, so if you get sources from github then you’ll also get whatever fixes are being made for issues found in current UE4 release. You’ll also get possible bugs that have been introduced in the meantime. It’s not ideal, I know.
I’ll read through your description, pick the best fix and get back to you.
