Ghost Trails

Where a ghost trail reads as motion rather than noise

An afterimage works because the eye keeps a copy of the character for a fraction of a second longer than the character actually stays there. Ghost Trails exists to manufacture that copy on demand. It is a system for creating afterimages, and its tags — Trail, Effect, Ghost, VisualEffect — describe exactly the job: a visible echo of a mesh, left behind as something moves.

That makes it a fit for the moments where a character crosses ground faster than the animation alone can sell. A dash, a sidestep, a burst of speed on an enemy. Without the echo, the pose change happens and the audience simply accepts it. With the echo, the movement has a visible wake.

The effect is deliberately not scenery. It attaches to what is already animating, which is why the most useful way to think about Ghost Trails is as an extension of the animation rather than a separate visual effect layered on top of it.

AnimNotifyState is where the ghost trail's timing lives

The core workflow is the part worth understanding first: Ghost Trail is added to animations through AnimNotifyState, and that notify state controls the duration.

A notify state occupies a span inside an animation instead of one instant. Placing one on the timeline means the ghost trail starts and stops as part of the animation itself. There is no second cue to fire from elsewhere, no separate script waiting for the right frame — the animation carries its own afterimage window.

For animators, this changes where the work happens. Trimming a dash, retiming a recovery, or lengthening a lunge all move the trail along with the motion, because the trail is tied to the span that was marked. When a move is reworked, the effect follows instead of drifting out of sync.

It also means the trail can be authored per move. A short hop and a long charge can each carry their own span, so the ghosting lasts exactly as long as that particular action demands.

Ghost Trail V2.0: duration and opacity on their own terms

Version 2.0 adds two adjustments that do most of the visual heavy lifting: customizing the ghost trail's duration and its opacity.

Duration governs how far behind the character the echo stretches — how many copies exist at once and how long the oldest one survives. Opacity governs how much those copies impose on the frame. Together they decide whether the effect whispers or shouts.

A high-opacity, short-duration trail looks like a hard impact, each copy almost solid before it vanishes. A lower-opacity trail that lingers produces something softer and more spectral, closer to a blur with a shape. The same move can be pushed either direction depending on what the character is supposed to feel like.

Because both values are exposed rather than baked, they can be tuned against the actual scene. A trail that reads well against a dark corridor may disappear against a bright one, and the opacity setting is where that gets corrected.

Multiple mesh support when a character is more than one piece

Multiple mesh support is the other addition in Ghost Trail 2.0, and it addresses a practical problem: characters are frequently assembled from more than one mesh. Ghost Trails handles those setups, so the afterimage can follow a character built from several parts rather than being limited to a single mesh.

That widens the range of characters the trail can be attached to without the effect becoming a special case. The trail stays consistent across the character instead of picking up one piece and leaving the rest clean.

The blueprint, actor, component and material pieces

The tag set behind Ghost Trails — Actor, Component, Blueprint, Material, Gameplay — maps out how the pieces fit together.

An actor and a component carry the effect

The trail exists as an actor in the scene, with component logic driving it. That structure is what lets it be placed, referenced, and controlled like other gameplay objects.

Blueprint logic drives the setup

Blueprint sits at the centre of the workflow, which is consistent with an effect that has to respond to animation events and expose values like duration and opacity for adjustment.

Material handles the look

Material appears in the tag list too, which fits an effect whose appearance is shaped in a material rather than only in logic — the ghost's rendering is a separate concern from when it appears.

For anyone setting the system up for the first time, a manual walkthrough covers the manual path alongside the animation-driven one.

Who gets the most out of Ghost Trails

The people who will find this most immediately useful are animators and technical artists working on character action in Unreal, particularly those who want the afterimage to belong to the animation rather than to a separate effects layer. If a project already has dashes, dodges, or fast-moving enemies waiting for a visual wake, the AnimNotifyState route puts that wake directly on the timeline where the motion is authored.

Teams working with characters built from multiple meshes get the additional benefit of a trail that covers the whole setup. And because duration and opacity are open to adjustment in 2.0, the same system can serve a subtle motion echo and an aggressive speed burst without needing two different approaches.

More From The Same Workflow

• Ready Platforms
• Fight Game Select Character
• Virtual Reality Character Flying
• Fade Camera Occluders
• Open World AI Multiplayer Spawn System