Fix: Unity VFX Graph Event Output Not Firing

A rocket particle should trigger a secondary explosion emitter when it dies. The rocket dies as expected, but the explosion emitter never receives the event. The graph compiles without warnings. The wires look correct in the editor.

The GPU Event Pipeline

VFX Graph events are point-to-point connections between emitters with three pieces:

1. Trigger block in the source emitter (e.g., Trigger Event On Die).
2. Event name (string) on the trigger block.
3. Spawn Event context in the downstream emitter with the same name.

The runtime matches by name. Typos in either side break the link silently — no compile error, no warning in the Output Log.

Fix 1: Verify the Event Pair

Open the VFX Graph asset. In the source emitter’s Update block:

Update Particle:
  ...
  Trigger Event On Die:
    Count = 1
    Event Name = "OnExplosion"

In the downstream emitter:

Spawn from Event:
  Event Name = "OnExplosion"

Click each block’s Inspector and verify the event names match exactly — case-sensitive, no leading/trailing whitespace.

Fix 2: Connect the Event Output Wires

The Trigger Event block exposes an output port; drag from it to the downstream emitter’s Spawn Event context input. Without the wire, the event is broadcast but nothing listens for it. The orange event wire is distinct from the white particle data wires — check it’s actually connected (the editor sometimes leaves dangling drags).

Fix 3: Capacity on Downstream

The Spawn Event has a Capacity. If the trigger fires more events than capacity per frame, the excess is dropped. For a rocket explosion that should spawn 64 sparks at the moment of death, the downstream emitter needs Capacity ≥ 64. Default capacity is 1024; bump it for high-burst scenarios.

Fix 4: Same Asset Required

GPU events only flow between emitters in the same VFX Graph asset. Two separate .vfx files can’t exchange GPU events — the runtime allocates per-asset event buffers. Merge them into one graph if cross-emitter events are needed, or use a CPU event via VisualEffect.SendEvent("name") from script.

Diagnosing via Debug Overlay

Open the VFX Graph editor, click the asset in your scene, and enable Window → Visual Effects → Debug. The overlay shows per-emitter active particle count and per-event drop count. Triggering the source and seeing event count climb but downstream particle count flat = events firing but downstream not spawning — usually capacity or name mismatch.

Verifying

Build a test scene with the rocket-explosion pair. Trigger the rocket, watch for the secondary effect. Use the Debug overlay to confirm events fire (number greater than zero on the trigger side) and spawn on the downstream side. If trigger increments but spawn doesn’t, name or capacity is wrong.

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

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

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

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

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

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

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

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.

“GPU events are string-matched between blocks. One typo breaks the chain silently. Check both sides letter by letter.”

Use an enum or constant for event names across a graph to avoid typos — expose it via a Subgraph and reference everywhere.