Per-emitter render state fed to the GPU billboard pass. Mirrors the CPU path's per-emitter knobs so a given billboard mode renders the same whichever simulationMode the emitter selects.
A per-particle script, the Niagara scratch-pad analogue: statements of the form vel.y = vel.y - 9.8 * dt (also += -= *= /=), separated by newlines or semicolons, compiled once into stack bytecode and run for every part
What a particle fragment is fogged through (Shaders/Private/Particles/ ParticleFog.hlsli): the froxel volume, the sky atmosphere's constants, aerial volume and LUTs, and the frame's fog parameters. The renderer that owns
Light module - the emitter's brightest particles become dynamic point lights that illuminate the scene. The module owns no per-particle state; it is a budgeted marker the renderer reads (see Scene::SubmitParticleLights)
Per-particle script (FParticleExpression): the author's own math at spawn or every update, where the fixed modules run out — a spiral, a colour that follows speed, a size pulse. A spawn script runs on the CPU for both si
Sub-emitter: wherever the parent's particles are born, die or hit something, spawn particles into a child emitter — sparks that burst into embers on impact, a firework shell that dies into a shower. The child is either a
Single source of truth for the MDF representation of a ParticleModule. Both the property-authored .particle asset and the graph-authored .vfx compiler route through here, so a module authored in either front-end serializ
One draw's worth of billboards: everything that has to agree between two particles for them to share a draw call. Batches are kept in submission order so an emitter sorted back-to-front stays back-to-front on screen.
Abstract CPU particle renderer interface. The concrete backend (RHIParticleRenderer) is implemented on the Platform/ RHI API (Shader/Pipeline/VertexBuffer/DescriptorSet) and draws into an off-screen target via SetTargetF
A run of quads in the current batch, sized up front so emitters can fill their own runs on worker threads: reserving moves the batch vectors and writing never does, so every reservation of a frame comes before any write.
The renderer's collision field expressed as GPU-samplable parameters, pushed once per view. Baked into every GPU emitter's sim params so the compute pass collides against the same SDF/depth the CPU CollisionModule uses (
The result of compiling a .vfx graph: the exact authorable emitter state the ParticleSystem consumes (the module list plus the spawn/lifetime/start/render settings). This mirrors the fields a property-authored ParticleAs
Authoring stage a node belongs to. Purely a layout/grouping concern for the editor's stage columns; the compiler collects nodes by ModuleType, not Stage.
One node in a .vfx emitter graph. ModuleType is either a settings marker ("Emitter", "SpawnRate", "Burst", "Initialize", "Render") or a particle module type name ("Shape", "Velocity", "Color", "Size", "Force", "Noise", "
The particle-attribute flow authored as a node graph. Stores the nodes, their connections and their per-node parameter blobs, and serializes the whole thing to a .vfx MDF document. Compilation to a runtime emitter config
Turns a .vfx node graph into the runtime emitter config the ParticleSystem consumes, and back. Compile walks the settings nodes into the config fields and each module node (in graph order) into a ParticleModule via the s
Abstract ribbon (trail-strip) renderer interface. The concrete backend (RHIRibbonRenderer) is implemented on the Platform/ RHI API and draws into an off-screen target set before Initialize.