A roar that starts a frame late feels detached from the body on screen. The mouth is already open, the arm has already come down, and the sound is still waiting on a gameplay event that fired too early or too late. For creature sounds in Unreal Engine, the reliable fix is to trigger them from Anim Notifies: markers on the animation timeline that play a footstep, an attack vocal or a roar at the same moment the body does the work.
This guide shows you how to place a Play Sound notify on an Animation Sequence or an Anim Montage, feed it a Sound Cue that picks random variations without an obvious repeat, and assign attenuation so the creature sits in the 3D world. You will also see when to use an Anim Notify State, how to organize notify tracks, and how to separate an effort that always plays from an impact that should wait for a confirmed hit.
Why should you trigger creature sounds from Anim Notifies?
Gameplay code is a weak place for anything that has to match a specific frame. An attack-started event may fire when the montage begins, several frames before the mouth opens or the claw connects. A footstep driven by a timer or a movement event will drift as soon as the walk play rate changes, or when two locomotion animations blend.
Anim Notifies live on the animation itself. When the sequence or montage reaches that time, the notify fires, including when you speed the animation up or slow it down. Use them for foot plants and locomotion efforts, a threat or wind-up, the committed attack cry, a hit reaction on the flinch, and a death vocal. An impact that should play only when the attack actually hits is often better driven from a confirmed gameplay trace, with the body effort still on the notify, so a missed swing does not play a meaty impact in empty air.
What is an Anim Notify in Unreal Engine 5?
An Anim Notify is a marker on an Animation Sequence or an Anim Montage. When the animation evaluates past that time, Unreal calls the notify. In the Animation Sequence editor, the markers sit on notify tracks under the timeline. You can add and name more than one track, so footsteps, vocals and particle cues do not stack.
| Tool | When it fires | Best for |
|---|---|---|
| Play Sound notify | One instant on the timeline | Footsteps, attack cries, death vocals and other one-shots |
| Custom Anim Notify | One instant, with your own logic | A surface trace, a physical material, or a call into your audio system |
| Anim Notify State | A time range, with Begin, Tick and End | Looping or held sounds that must stop when the pose ends or the montage is interrupted |
Play Sound (AnimNotify_PlaySound) plays a Sound Base: a Sound Wave, a Sound Cue or a MetaSound. Build a custom Blueprint or C++ Anim Notify when you need a line trace or other logic the built-in notify cannot do.
Listen to the actions you will sync to animation
These previews come from Monster Sound Effects Pack — Volume 1, which has 14 actions with six variations each (84 WAV files). Each player below is one take of an action. In a project, put all six takes into a Sound Cue, then point the Play Sound notify at the Cue, not at a single wave.
Walk — locomotion effort, on foot plants
Threatening — wind-up or display
Attack — committed effort
Abdomen hit — hit reaction
Death — death montage
These previews include a light musical watermark. The WAV files you buy are clean.
How do you add a Play Sound notify?
A walk cycle is a good first test: you can see the plants and hear a repeat immediately if the sound is wrong.
- Import your WAV files into the Content Browser and keep each action’s takes together, using a pattern like
SB_Monster_Walk_01.wavthroughSB_Monster_Walk_06.wav. - Open the Animation Sequence that your Animation Blueprint actually plays — the walk or run cycle, not a reference pose.
- In the timeline Notifies section, add a named notify track if you need a clean lane, such as Footsteps or Vocals.
- Scrub until the event is visually true: the foot is planted, the jaw is opening, or the arm is committed. Do not place the notify at time zero unless the sound should start on the first frame.
- Right-click the notify track at that time and choose Add Notify → Play Sound.
- Set Sound to your Sound Cue or MetaSound, even if you only have one wave today, so you can add variations later without revisiting every animation.
- Set Follow and Attach Name with the job in mind. For a roar or attack vocal, enable Follow and attach to a head, jaw or mouth socket so the voice travels with the creature. For a foot plant that should stay on the ground, leave Follow off so the sound stays at the contact location.
- Use Volume Multiplier and Pitch Multiplier sparingly if the Cue already randomizes those values.
- Play the animation and listen. If the onset feels late, nudge the notify earlier by a few frames. If the preview is silent, confirm editor audio is enabled, move the viewport closer, or use Preview Ignore Attenuation.
- Repeat for each foot plant. A typical walk cycle has two contacts.
If you blend a walk into a run and both animations have footstep notifies, you can hear two plants at once. Raise the Trigger Weight Threshold so the notify only fires when that animation is the dominant blend — 0.5 is a common starting point. In a multiplayer project, turn off triggering on a dedicated server so the server does not spawn audio components for no one.
How do you add Sound Cue random variations?
If the notify plays a single Sound Wave, a walk cycle will stamp the same file every plant. Pitch modulation on one wave helps only a little, because the shape of the performance does not change. The Unreal-native fix is a Sound Cue with a Random node, not a random choice inside every notify.
- In the Content Browser, create a Sound Cue per action (under Sounds or Audio, depending on your Unreal Engine 5 version).
- Add a Random node and connect each of the six Sound Waves for that action, using names like
SB_Monster_Attack_01throughSB_Monster_Attack_06. - Enable Randomize Without Replacement on the Random node, so the node works through the pool before repeating instead of allowing the same take twice in a row.
- Optionally add a Modulator between the Random node and the Output. A conservative starting point is a pitch range close to 0.96–1.04 and a modest volume range. If you push pitch too far, a large monster starts to sound like a smaller animal.
- Assign Sound Attenuation and, if you use it, Sound Concurrency on the Cue, not on each wave. Then set the Play Sound notify’s Sound field to this Cue.
A MetaSound Source is also a Sound Base, so you can assign it to Play Sound and build wave selection, pitch and gain in the graph. If you also work in Unity, the same variation problem is usually handled in a component rather than a cue graph: see Unity Sound Variations Without Repeats.
How should you set attenuation so the creature sits in the world?
A Play Sound notify spatializes using the attenuation on the Sound Base. If Follow is enabled, the sound moves with the attachment socket. If Follow is off, it stays at the world location where the notify fired.
Create a Sound Attenuation asset and assign it on the Cue. Shape is usually a sphere for a creature vocal. Inner radius is the distance where the sound stays at full voice; for a large monster, a few meters is a reasonable place to start. Falloff distance is how far beyond that the voice recedes. Give loud display vocals and quiet locomotion different assets, or at least different falloff distances, so a walk effort does not carry as far as a roar.
If several creatures can walk or roar at once, add a Sound Concurrency asset on the Cue so all six takes share the limit. Preview in the level: the roar should still read at the distance you care about, and a walk effort should not fill the entire map.
When should you use an Anim Notify State instead of Play Sound?
Play Sound is a one-shot: it fires, starts the sound, and does not own the rest of that sound’s life. If the montage is interrupted, a long roar may keep playing after the attack has already blended out. An Anim Notify State covers a span of the timeline. Start or fade in a looping breath or charge on Notify Begin, and stop or fade out on Notify End, which should still run if the montage is interrupted.
The usual path is a short custom Anim Notify State in Blueprint or C++ that starts an audio component on begin and stops it on end. That fits a looping inhale during a held charge, or a breath loop that should cut when the idle ends. A short attack cry still belongs on Play Sound. An impact that depends on hitting a target still belongs on gameplay.
Where do notifies belong, and how do you set up footsteps, attacks and roars?
Put the notify on the asset that actually plays. Walk, run and idle cycles usually play from the Animation Blueprint as Animation Sequences, so footsteps and locomotion efforts go there. Attacks, hit reactions and deaths are often played as Anim Montages from combat or AI code; put those vocals on the montage. Sequence notifies still fire when a Montage plays that sequence as a segment, and the Montage editor has its own notify tracks for markers that belong only to that montage. Do not place the same Play Sound on both, or the vocal will fire twice. Name your tracks — Footsteps, Vocals and VFX is a clear layout. Sync markers are not notifies; they do not play audio.
On walk and run, place a notify on each foot plant and point it at a Walk Sound Cue with six takes and Randomize Without Replacement. Locomotion fires constantly, so variation matters more here than on a death cry. The walk files in a creature pack are usually body efforts or vocalized steps, not surface Foley. If you also need dirt, stone or metal footfalls, use a custom notify that traces for a physical material, and keep the creature effort on its own track so the two can be mixed separately.
On the attack Montage, a threatening or wind-up vocal can sit near the start, when the body telegraphs, and the attack cry should sit on the committed effort, not automatically on the hit frame. If the claw or weapon can miss, keep a confirmed impact or a victim hit reaction on a gameplay trace, rather than on the swing alone. A flinch or abdomen-hit vocal belongs on the hit-reaction Montage. For death, one Play Sound on the death Montage is usually enough; random variations still help when several enemies can die in the same fight.
What should you check if the sound is late, missing or repeating?
- The notify is on the asset that is actually playing, and its time matches the pose in the viewport.
- Trigger Weight Threshold is high enough to prevent double plants during blends, and not so high that a lightly blended animation never fires.
- Follow and the socket name are correct. A missing socket will fail to attach.
- The Sound field points at the Cue, the waves are connected to the Random node, and attenuation is not so short that the listener is already outside the falloff.
- Concurrency is not preventing every new play, dedicated-server triggering is off for audio-only notifies, and combat code is not also firing the same sound on the same frame.
- A long one-shot is not stacking on itself. Play Sound does not cancel the previous roar; if that overlap is a problem, use concurrency or a custom notify that stops the previous component.
Frequently asked questions
Does a Play Sound notify replace a custom Anim Notify?
Not always. Play Sound is enough when you only need to play a Cue at a time and socket. Write a custom notify when you need a trace, a surface, or a call into your own audio system.
Do Anim Notifies still fire if I change the animation play rate?
Yes. They are stored against the animation time, so they fire when that pose is reached, whether the animation is faster or slower.
What if I need a vocal that is not in the pack?
If you need a custom roar or effort that the library does not include, you can generate one in Voice Studio: create a free account and start right away. Add it to a Sound Cue with the rest of the takes, and listen to it on the notify.
Do the purchased WAV files include the watermark?
No. Only the website previews carry a light musical watermark. The WAV files in the pack are clean.


