unreal-niagara Checked

Create and control VFX in Unreal Engine 5 with Niagara: systems and emitters, modules and the spawn/update stages, exposed User parameters, and spawning or driving effects from Blueprints or C++. Use when building particle effects, NS_/NE_ assets, spawning a Niagara system at runtime, setting User parameters, or when the user mentions Niagara, VFX, or a particle system in Unreal.

Unreal Niagara VFX

Build and control real-time visual effects in UE5 with Niagara: understand the

System/Emitter/Module hierarchy, expose parameters you can drive from gameplay, and spawn

effects at runtime. Targets **UE 5.8**. (Niagara replaces the legacy Cascade system.)

Create and control VFX in Unreal Engine 5 with Niagara: systems and emitters, modules and the spawn/update stages, exposed User parameters, and spawning or driving effects from Blueprints or C++. Use when building particle effects, NS_/NE_ assets, spawning a Niagara system at runtime, setting User parameters, or when the user mentions Niagara, VFX, or a particle system in Unreal.

Unreal Niagara VFX

Build and control real-time visual effects in UE5 with Niagara: understand the

System/Emitter/Module hierarchy, expose parameters you can drive from gameplay, and spawn

effects at runtime. Targets **UE 5.8**. (Niagara replaces the legacy Cascade system.)

When to use

• Use when creating a Niagara System (NS_) and Emitters (NE_), wiring modules in the

spawn/update stages, exposing **User** parameters to gameplay, or spawning/driving an effect

(impact, muzzle flash, fire, magic) from Blueprint or C++.

• Use when the project has Niagara NS_/NE_ assets or references UNiagaraComponent.

**When *not* to use:** material/shader authoring (the look of a surface, not particles) is a

separate topic; shader-programming covers cross-engine shader concepts. Audio for the effect

→ audio-design.

Core workflow

1. **Understand the hierarchy.** A **Niagara System** (NS_) is the effect you place/spawn; it

contains one or more **Emitters** (NE_, often emitter *templates*). Each emitter runs in

stages: **Emitter Spawn/Update**, **Particle Spawn/Update**, optional **Event Handler**, and

**Render**.

2. **Build behaviour from Modules**, which execute top-to-bottom in each stage (Spawn Rate,

Add Velocity, Gravity Force, Color over Life, etc.). Order matters — a later module reads the

values earlier ones wrote.

3. **Know the parameter namespaces:** System, Emitter, Particle, and **User**. Only

**User-namespace** parameters are exposed to and settable from Blueprint/C++; the others are

internal to the simulation.

4. **Spawn at runtime** with UNiagaraFunctionLibrary::SpawnSystemAtLocation (world position)

or SpawnSystemAttached (follows a component/socket), which return a UNiagaraComponent.

5. **Drive the effect** by setting its User parameters on the returned component (color, spawn

rate, a target position) and Activate/Deactivate it.

6. **Verify** in the Niagara editor preview and in-level; check bounds (especially GPU

emitters), and confirm the effect culls/destroys correctly.

Patterns

### 1. Spawn a one-shot effect at a world location (C++)

#include "NiagaraFunctionLibrary.h"
#include "NiagaraComponent.h"

// ImpactSystem is a UPROPERTY(EditAnywhere) TObjectPtr<UNiagaraSystem>.
void AProjectile::SpawnImpact(const FVector& Location, const FRotator& Rotation)
{
    UNiagaraComponent* FX = UNiagaraFunctionLibrary::SpawnSystemAtLocation(
        GetWorld(), ImpactSystem, Location, Rotation);
    // FX auto-destroys when finished for a one-shot (system marked non-looping).
}