Fix: Unity VFX Graph Event Not Firing from Script

Hit registers, you call SendEvent on the VisualEffect, nothing spawns. The graph plays its idle effect normally; your custom event is invisible. The chain from script to GPU has three parts and any of them can be wrong.

The Symptom

SendEvent returns no value, no error, no particles. The graph keeps emitting whatever it was emitting before. Toggling the VisualEffect off/on or calling Play() works, but custom events do not.

The Three Required Pieces

1. Spawn Event in the graph. Right-click in the graph → Create Node → Event → Event. Name it (e.g. “OnHit”). The name is case-sensitive and must match SendEvent exactly.

2. Spawn Context wired from the event. Drag from the Event node’s output to a Spawn Context input. Spawn Contexts are the only nodes that consume events; without one wired, the event has nowhere to go.

3. SendEvent from script with the matching name.

using UnityEngine;
using UnityEngine.VFX;

public class HitVFX : MonoBehaviour
{
    public VisualEffect vfx;
    private static readonly int _hitId = Shader.PropertyToID("OnHit");

    public void Hit(Vector3 position, Vector3 normal)
    {
        var attr = vfx.CreateVFXEventAttribute();
        attr.SetVector3("position", position);
        attr.SetVector3("velocity", normal * 5f);
        vfx.SendEvent(_hitId, attr);
    }
}

Caching the event id with PropertyToID is a small win; the string overload also works.

Reading the Attribute on the Graph Side

To use the position/velocity you sent, add Set Position from Event and Set Velocity from Event blocks in the Initialize Particle context. The blocks expose dropdowns to pick which Spawn Event the attribute came from.

Verifying It Worked

Select the GameObject. Open the VFX Graph asset. The Target Visual Effect dock at the bottom of the graph shows live stats per Spawn Context: Spawn Count, Spawn Per Second, and event arrivals. SendEvent should bump the “Spawn Count” or “Direct Spawn” figure.

If the figure stays at zero, the script side is fine but the graph side is not receiving. Re-check: Event node name, edge into a Spawn Context, asset is saved.

Common Pitfall: Output Particle Quad Stops Listening

If the graph compiles with errors, the runtime swap-in fails silently and SendEvent does nothing. Open the graph and look for red nodes. A common cause is changing an exposed property type without re-saving its consumers; everything appears connected but the compile fails.

Pooling Caveat

VisualEffect components do not pool well across scenes — SendEvent on a freshly enabled VisualEffect may fire before the GPU sees the activation. Wait one frame after enable before SendEvent, or call vfx.Play() before sending custom events to force initialization.

Understanding the issue

Visual effects exist at the intersection of art and engineering. The asset team authors what they want to see; the engineering team makes it run within the frame budget. When these two pipelines interact poorly, the symptoms range from missing particles to entire systems silently failing.

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

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

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

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

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

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

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

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

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.

“Spawn Event named, wired into a Context, SendEvent with the exact name. Graph dock confirms the count.”

Related Issues

For VFX Graph not rendering at all, see VFX not rendering. For exposed property changes ignored, see exposed property not applied.

Event → Spawn Context. Send by name. Watch the dock.