In my anim blueprint I am getting the velocity and setting a speed variable to drive animations. When the behavior tree move to executes the animations work fine and the AI character moves, but the animation notifies aren’t firing. To test I am printing out the speed variable (see pic) and it prints the speed, then zero, then the speed, then zero repeating while the moveto is executing.
My animations look fine, but they and the state machine use speed as an input. Everything looks ok and the state machine seems to behave as expected, except the animation notifies won’t fire and I have two different alternating values for the speed variable. All I can figure is that it must be a bug.
124322-
Issue 1) The only thing I can think of off the top of my head is that your notifies might have a higher than normal Trigger Weight Threshold set. Could you either send me an example project (Assets migrated to a blank template and set up to show the problem) or attach more detailed images(Notify details panel and a breakdown of the AnimGraph would be good). If you’d like to send a project, you can PM me a download link on the forums. Please respond here if you PM me as it will notify me better.
Issue 2) The fact that it’s printing out 0 is likely because you still have the AnimBP open while you PIE. The AnimBP Preview counts as an instance of the AnimBP and will execute any print strings while PIE occurs. Try using an IsValid? check on the PawnOwner off of any events in the event graph. See the Third Person Template project as an example.
Thanks for the answer to issue 2. Closing the anim bp in the editor eliminated the zero printing out. I have more info regarding the anim notifies problem. I had created an anim notify named Footsteps. I later added a FootstepR and a Footstep L, then I deleted the redundant original Footsteps in the “manage notifies” menu. For some reason it ignored the new 2 every time. I renamed them FstepR and FstepL and they work. It also always still shows the original Footsteps notify in the list of notifies, although I can not interact with it in any way. Hope this helps tracking down the bug.
I was still unable to reproduce it by trying the same process that you described. We had some issues with the anim notify manager and this was likely resolved by a few fixes made in 4.15.
Could you try this in 4.15 and let me know if it crops up again?
