Fix: GameMaker Particle System Not Emitting

Here is how to fix GameMaker particle systems that produce no visible output. You wire up a system, type, and emitter in your Create event, call part_emitter_burst on click, and the screen stays empty. No errors. The particle system index is valid. The fix is almost always one of three things: the system has no layer, the type has zero life, or the emitter has no region.

The Symptom

You set up a particle system in Create, call part_emitter_burst(ps, em, pt, 50) in a Step or button-press event, and see nothing. The particle system index is a positive integer (so creation succeeded), but no particles ever appear on screen.

What Causes This

System has no layer. part_system_create in GMS 2.3+ creates a system at depth 0 with no layer assignment. If your room layers do not include depth 0 visibly, the particles draw under everything else. Use part_system_create_layer instead.

Particle type has zero life. If you forget part_type_life, the type defaults to a 0–0 life span. Particles are emitted and immediately destroyed in the same step.

Emitter region is a single point. Without part_emitter_region, particles emit from (0,0) which may be off-screen in your view. Set the emitter region to the position you actually want.

Type or emitter destroyed prematurely. Calling part_type_destroy in the same Create event destroys the type before bursts can use it.

The Fix

Step 1: Create the system on a layer.

// Create event of oVfx
ps = part_system_create_layer("Effects", false);

// Particle type (a small white spark)
pt = part_type_create();
part_type_shape(pt, pt_shape_pixel);
part_type_size(pt, 0.5, 1.5, 0, 0);
part_type_color1(pt, c_white);
part_type_alpha2(pt, 1, 0);
part_type_life(pt, 15, 30);          // Critical: non-zero life
part_type_speed(pt, 2, 5, 0, 0);
part_type_direction(pt, 0, 360, 0, 0);

// Emitter
em = part_emitter_create(ps);
part_emitter_region(ps, em, x - 8, x + 8, y - 8, y + 8, ps_shape_ellipse, ps_distr_linear);

Make sure the layer name “Effects” exists in your room. If not, create one or use the room’s default Instances layer.

Step 2: Burst when needed.

// On click or hit event
part_emitter_burst(ps, em, pt, 40);

Step 3: Update the emitter region for moving sources. If your particle system follows a moving object, update the region every step:

// Step event of moving object
part_emitter_region(ps, em,
    x - 8, x + 8,
    y - 8, y + 8,
    ps_shape_ellipse, ps_distr_linear);

Step 4: Free resources on cleanup.

// Clean Up event
part_emitter_destroy(ps, em);
part_type_destroy(pt);
part_system_destroy(ps);

Step 5: Persistence for cross-room effects.

part_system_persistent(ps, true);
persistent = true;  // instance variable on the controller object

Both flags are needed: the system itself must be persistent, and the owning instance must survive the room change so the indices remain valid.

Verifying With a Visual Test

Drop a part_emitter_burst directly in your Step event temporarily so it bursts every frame at the player’s position. If you see a constant stream, the system works and your trigger code is the issue. If you see nothing, recheck life span and layer assignment.

Common Off-By-One Mistakes

The argument order for part_emitter_region is (ps, em, xmin, xmax, ymin, ymax, shape, distribution). Putting xmax before xmin produces an invalid region that emits from a single corner. Always order min-then-max, X then Y.

Understanding the issue

Particle systems are stateful machines. Each particle has its own lifetime, and the system has its own configuration. Bugs that involve the lifecycle (creation, death, pool reuse) tend to be timing-sensitive and hardest to reproduce.

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 GameMaker. 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

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 GameMaker-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 GameMaker, 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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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.

“Layer, life, region. The three things every visible particle system needs. Forget one and you see nothing.”

Related Issues

For other GameMaker rendering issues, see Room Transition Flicker and Layer Depth Draw Order.

Layer for the system. Life for the type. Region for the emitter. Three pieces, one effect.