AnimNotify is unreliable and inconsistent

Engine version 4.10.2

  • Create a custom AnimNotify like so (I called mine in this example ‘ShootStart’):

  • Place the AnimNotify you created in an animation. You can see my custom made one is ‘ShootStart’ which appears with the default AnimNotify ‘PlaySound’ and ‘PlayParticleEffect’. The actual “Custom” ones are the simple custom AnimNotify that you can make by pressing that ‘New Notify’ button.

  • Here you can see I added 3 AnimNotify to the animation. ‘ShootStart’, ‘TestNotify’ and ‘ShootBolt’. the 2 yellow ones indicate AnimNotify that you make with the ‘NewNotify’ button, the ‘ShootStart’ is a custom one I made outside of Persona, that’s why it has a custom color.

  • !!! RESTART THE EDITOR !!!

  • Go to your Animation BP, and inside the EventGraph, right-click to add the AnimNotify events, and you can see here that only the ‘New Notify’ button-created AnimNotify will show.

  • First problem: Where is my ‘ShootStart’ AnimNotify event to add in the EventGraph that I created myself at the start? This is the first unreliable and inconsistent problem. (I did restart the editor like I said in the instructions)

  • Second problem: If I hook up function calls for the AnimNotify that I can add an event in the EventGraph to… they will trigger twice with these DEFAULT settings:


You can see here that the Notify Trigger Chance is at 1.0, which means it will always trigger. But it always triggers TWICE. Always.

I FOUND IT.

This is actually not in the documentation for individual Custom Anim Notify. The section for Notify State helped me figure this one out.

If you open your custom AnimNotify BP, you can override the function ‘Received Notify’ and enter your logic in there.

This is why it does not show in your Animation BP’s EventGraph, because you have to enter your logic in your Custom AnimNotify BP itself by overriding this function. NOT in the Anim BP EventGraph where you receive events for your ‘New Notify’-created ones. Refer to main post to see that. Big difference between the 2.

As for the triggers triggering twice, this was entirely a networking issue on my part. My networking logic was wrong and it was resulting in 2 AnimNotify calls being called over the network from the client and from the server, so 2 at once.

Hey shahrizai,

I have created a request for a documentation update as UEDOC-2870. Although, it is somewhat documented in an existing blog post, I wanted to push that to our official docs.

-.