Fix: Unity Particle Collision Message Not Firing

Here is how to fix Unity particles that visually collide with surfaces but never fire OnParticleCollision. You hook up a damage script to a target so bullets-as-particles trigger health loss, but the callback never runs. The Send Collision Messages flag is per-system and off by default; without it, the particle system bounces off colliders silently.

The Symptom

Particles visibly collide with the world (you see them stop or bounce), but the OnParticleCollision(GameObject other) message never reaches your script. No errors. No warnings. The particles know about collisions; your code does not.

What Causes This

Send Collision Messages disabled. Without this checkbox in the Collision module, the system performs collisions but does not dispatch messages.

Script on the wrong GameObject. OnParticleCollision fires on the GameObject that owns the collider being hit, not on the particle system. A script on the emitter never receives messages.

Collision layer mismatch. The Collision module has a Collides With layer mask. If the target is on Layer 8 but the mask only includes Layer 0 (Default), no collision is detected.

2D vs 3D mismatch. Particle System collisions are 3D by default. 2D colliders need Type = World and a 2D physics layer setup, plus the right collision mode.

The Fix

Step 1: Enable the Collision module correctly. On the Particle System, expand Collision:

Type:                     World
Mode:                     3D (or 2D for sprite-based games)
Send Collision Messages:  true
Visualize Bounds:         on (helpful while debugging)
Collides With:            Default + your custom layer
Collision Quality:        High
Voxel Size:               0.5

Step 2: Place OnParticleCollision on the target.

using UnityEngine;

public class EnemyHealth : MonoBehaviour
{
    [SerializeField] private float hp = 100f;

    void OnParticleCollision(GameObject other)
    {
        // other = the particle system GameObject
        hp -= 10f;
        if (hp <= 0) Destroy(gameObject);
    }
}

Attach this to the enemy, not the bullet’s ParticleSystem.

Step 3: Read collision details if needed.

using System.Collections.Generic;

ParticleCollisionEvent[] events = new ParticleCollisionEvent[16];

void OnParticleCollision(GameObject other)
{
    ParticleSystem ps = other.GetComponent<ParticleSystem>();
    int count = ps.GetCollisionEvents(gameObject, events);
    for (int i = 0; i < count; i++)
    {
        Vector3 hitPoint = events[i].intersection;
        Vector3 hitNormal = events[i].normal;
        // spawn impact effect at hitPoint
    }
}

Step 4: Match physics layers and tags. Ensure the target’s layer is included in the Particle System Collision module’s Collides With mask. Open Edit → Project Settings → Physics and verify the Particle Collision Layer Matrix permits the interaction.

Step 5: Test with a known-good setup. Drop a default cube on the floor with the EnemyHealth script attached. Aim a default Particle System with Collision enabled at it. If the message fires, your config is correct; iterate from there.

Performance Considerations

World collision with high quality is expensive at high particle counts. For magic-bullet effects with hundreds of particles, consider Planes mode (cheap), or use raycasts for a single bullet and ParticleSystem only as visual.

Understanding the issue

VFX bugs frequently emerge only in shipping configurations because development uses higher quality settings where edge cases hide. Stripping, compression, or quality scaling - any of these can convert a working effect into a broken one.

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

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

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

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

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.

“Send Collision Messages flag, script on the target, layer mask matches. Three checks for working callbacks.”

Related Issues

For particles failing to play, see Particle System Not Playing. For trail rendering issues, see Particle Trail Through Walls.

Module on. Flag on. Script on the target. Layers match. Messages flow.