Fix: Unity Visual Effect Graph Event Not Firing

Here is how to fix Unity Visual Effect Graph event not firing. You define a custom event “Impact” in your VFX Graph. On hit, you call vfx.SendEvent("Impact"). Nothing happens. You switch to another Event name that works (OnPlay) and confirm the graph reacts — so the graph is alive. The custom event is simply silent.

The Symptom

VFX Graph custom events do not fire when SendEvent is called. The graph is loaded, plays on OnPlay, responds to exposed parameter changes — just not to custom events. No errors in the console.

What Causes This

Event name typo. Strings. Case-sensitive. SendEvent("impact") does not match an Event context named “Impact.”

Event context missing. The VFX Graph must have an Event context with the matching name. Without one, the SendEvent call has nowhere to connect. Check your graph’s top-level contexts.

Effect stopped. If the effect is in Stopped state, SendEvent does nothing. The effect must be playing. visualEffect.Play() first, then SendEvent works.

GPU events are graph-internal. Trigger Event blocks inside particle update steps fire GPU events that feed other systems within the same graph. They cannot trigger events on a different VFX instance.

Binding attribute not passed. For events with attributes (position, velocity), use SendEvent with VFXEventAttribute. Bare SendEvent("Name") fires the event but attributes stay at defaults.

The Fix

Step 1: Verify event name. Open the VFX Graph. Check top-level Event contexts. Note exact names. In script, use const strings to avoid typos:

using UnityEngine;
using UnityEngine.VFX;

public class HitEffect : MonoBehaviour
{
    [SerializeField] private VisualEffect vfx;
    private const string IMPACT_EVENT = "Impact";

    public void OnHit()
    {
        if (!vfx.HasEvent(IMPACT_EVENT))
        {
            Debug.LogError($"VFX missing {IMPACT_EVENT} event");
            return;
        }
        vfx.SendEvent(IMPACT_EVENT);
    }
}

HasEvent returns true if the graph has a context with that name. Use as a guard to catch typos at runtime.

Step 2: Ensure the effect is playing. If the effect is Stopped, Play() before SendEvent:

public void TriggerImpact(Vector3 position)
{
    vfx.transform.position = position;
    if (!vfx.aliveParticleCount > 0)
        vfx.Play();

    vfx.SendEvent(IMPACT_EVENT);
}

For impact effects that should trigger repeatedly without calling Play each time, set the graph’s Initial Event Name in the Visual Effect inspector to your custom event, or configure the graph to stay alive indefinitely with an OnPlay/OnStop pair.

Step 3: Pass attributes with VFXEventAttribute. For events that need data (spawn position, velocity vector):

public void TriggerAt(Vector3 pos, Vector3 vel)
{
    VFXEventAttribute attr = vfx.CreateVFXEventAttribute();
    attr.SetVector3("position", pos);
    attr.SetVector3("velocity", vel);
    vfx.SendEvent(IMPACT_EVENT, attr);
}

In the graph, add attribute Get nodes in the spawn context to read the passed values. Without passing attributes, particles spawn with default positions (origin) and zero velocity.

Step 4: Use GPU Trigger Events for graph-internal chains. If you want one system inside the graph to spawn particles in another system (e.g. trail emits sparks), use Trigger Event Always, Trigger Event Rate, or Trigger Event On Die blocks in the update context. These fire GPU events consumed by the linked system’s Event context.

GPU events cannot be triggered from script. They are entirely within-graph.

Debugging Events

Enable the VFX Graph debug overlay:

fx.Visual.Effects.Profiler 1  // console command

Shows event fire counts per frame. If your SendEvent call does not increment the Impact event counter, the call is not reaching the graph (wrong effect, wrong name, effect stopped).

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“VFX Graph events are strings into a list of contexts. Get the string right, confirm the context exists, and fire only when the effect is alive.”

Related Issues

For Niagara issues in Unreal, see Unreal Niagara Not Spawning in Packaged Build. For Unity particle system issues, Particle Stop Not Stopping Immediately.

HasEvent check. Play before SendEvent. Attribute passing for data. Three habits.