Fix: Godot 4 Particle Process Material Flicker on Mobile

Particles work great on PC. Build to Android — they pop in and out, count varies frame to frame, sometimes nothing emits at all. GPUParticles relies on compute paths that not every mobile GPU supports cleanly.

The Symptom

GPUParticles flicker, drop frames worth of particles, or render zero-duration. Sometimes works on Pixel devices, broken on Samsung. Editor preview is normal. CPUParticles in the same scene work fine.

What Causes This

GPUParticles compute on the GPU via shader storage buffers. Mobile drivers vary in how reliably they support the necessary features:

• Adreno 6xx and newer: usually fine on Vulkan, sometimes broken on GLES.
• Mali G-series: variable; older drivers crash.
• PowerVR: historically problematic.

The Compatibility renderer (GLES 3) silently falls back to a slower path that doesn’t handle GPU particles consistently.

The Fix

Step 1: Switch to CPUParticles. Right-click your GPUParticles2D/3D → Convert to CPUParticles2D/3D. Godot copies most settings over; review the result. Process Material maps to CPUParticles fields directly.

CPUParticles2D:
  amount:        200
  lifetime:      1.5
  emission_shape: Sphere
  initial_velocity: 100
  scale_amount_curve: ...

Step 2: Pick the right renderer. Project Settings → Rendering → Rendering Device → Driver. For Android target, set rendering_method.mobile = mobile (Vulkan) for newer devices, compatibility (GLES) for the broad market. Test on the lowest-spec device you support.

Step 3: Cap counts and durations. Mobile RAM is finite. Lifetime × emission rate = max alive count. Keep this under 500 unless you have profiled.

Per-Platform Configs

Use platform branches in your spawning code:

extends Node

@export var gpu_scene: PackedScene
@export var cpu_scene: PackedScene

func spawn() -> void:
    var scene = cpu_scene if OS.has_feature("mobile") else gpu_scene
    add_child(scene.instantiate())

One asset for desktop, one for mobile. The OS feature flag picks at runtime.

Verifying on Device

Run a development export with verbose logging. OS.has_feature("mobile") + RenderingServer.get_video_adapter_name() in a print. Confirm the renderer name matches your expectation; switch if needed.

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

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

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

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

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For Godot-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 Godot, 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

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.

“CPUParticles on mobile. Compatibility renderer for the long tail. Cap counts. Particles render every frame.”

Related Issues

For shaders failing to compile on mobile, see shader compile. For Godot mobile crash, see Android launch crash.

CPU on mobile. Compatibility renderer. Particles steady.