Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Modifiers are one of the most important features supported by the Particle Effect System in CRYENGINE. Although Particle Effects provide a wide range of feature implementations that can be used to make all kinds of effects, their true power is only achieved when modifiers are used to dynamically alter the effect behavior.

Modifiers menu options


On this page, some of the Modifiers are marked as Time-Based Modifiers. These modifiers have additional parameters called the Domains. When enabled, these options can display additional fields, depending on the modification itself and the domain type. For more information about the Time-Based Modifiers and domains, please refer to the Time-Based Modifier's Common Settings section below.


Many properties implemented by particle effect features can contain a stack of modifiers. Each modifier takes that property value and then manipulates it in a specific way and sends the modified value to the next element in the stack. Some of these modifiers combine the output value of the previous modifier with their own input by multiplying them.

Depending on the property in question and the settings of the modifier, its logic can be applied on each component. For example, each modifier logic can be used on a newly spawned particle or each particle in every frame.

The following list outlines the modifiers that are available in a component:


With this option, users can modify the original property based on an effect's attribute.

This modifier is an alternative way of using attributes. Another way would be to use Linear (Time-Based Modifier) with source option set to Attribute.



Attribute Name

Defines the name of the attribute to read from. If the attribute does not exist in this emitter, the input will get a value of 1 instead.

Scale and Bias

Allows the attribute to be scaled and biased. Usually useful when the input is not in the 0 to 1 range.

Spawn Only

Specifies if the attribute is to be applied only when a particle is first born or if it should always affect all living particles.

Config Spec

This option allows users to modify the original property based on the platform type or the particle quality settings. The best outcome can be achieved when it is used to scale other feature properties higher or lower for performance scalability.




Scale value used when on Low Spec PC.


Scale value used when on Medium Spec PC.


Scale value used when on High Spec PC.

Very High

Scale value used when on Very High Spec PC.

XBox One

Scale value used when on XBox One.

XBox One X

Scale value used when on XBox One X.

PlayStation 4

Scale value used when on PlayStation 4.

Linear (Time-Based Modifier)

This option allows users to combine properties that are modified with a domain; however, it doesn't apply any additional modification. In this modifier, only the time-based properties are used. Please refer to Time-Based Modifiers Common Settings for more information.

Noise (Time-Based Modifier)

This modifier uses a potential field based on Perlin noise to randomize the input property. Unlike the Random modifier, which tends to get fuzzy or diffuse, the Noise modifier adds smooth variations to the particles.




Available under the  dropdown menu.

Defines the domain input to sample the Perlin noise field. For more information, see the Time-Based Modifiers Common Settings section below.


Defines the noise mode:

  • Smooth - Simple Perlin Noise field.
  • Fractal - Adds additional roughness to the Perlin Noise field.
  • Pulse - Uses the noise field to pulse between 0 and 1. Useful to add flickering effects.


Indicates the amount of variation that will be added to the particle. If the amount is greater than 1, then it can provide a positive and a negative variation at the same time.

Pulse Width

Only available when the Pulse noise mode is active. Given value specifies the balance between the frequency of pulse being turned on or off. For example, a value of 0.5 allows the pulse to be turned on and off in an even frequency; values greater than 0.5 result in the pulse being turned off more often than it's turned on.


Use Domain Scale and Domain Bias to change the frequency and phase of noise. However, if the time scale is too high, Noise starts to behave closer to pure randomness and fuzziness; as a result, diffuse might start to arise.




Sample of Noise modes for a particle

Wave (Time-Based Modifier)

This modifier is used to provide different types of periodic values. Its options are based on trigonometric mathematics and are useful to add regular behaviors as opposed to variance.




Available under the  dropdown menu.
Lets users select a domain input to sample the wave trigonometric equations. For more information, see the Time-Based Modifiers Common Settings section below.


Defines the noise modes:

  • Sin
  • Saw
  • Pulse

Amplitude, Bias

Lets users add the Waveform settings.


When enabled, this option inverts the waveform.


Use Domain Scale and Domain Bias to change the frequency and phase of a wave. Se below for more information.


Cosine is the same as Sine with a 0.25 phase.




Wave equations samples

A waveform setting sample


This option can only be applied to the new particles. It provides a fast way to add simple variations to the particle behavior.




Specifies the amount of variation that will be added to the particle. If the amount is greater than 1, it can provide positive and negative variations at the same time.

Double Curve (Time-Based Modifier)

Unlike the Curve modifier, the Double Curve modifier uses two Bezier curves. The domain selection is used to sample both curves at the same time, while the Random field of the particle is used to interpolate between the lower and upper Bezier curves. This is useful in providing additional variance to the particle behavior.

See below for more information about domains.



Double Curve

Uses a double Bezier curve to provide additional variance. See Particle Editor for more information about Curve Editor.

Curve (Time-Based Modifier)

This option uses the domain input to sample a Bezier curve. In particles, Bezier curves have an unlimited number of points; however, each point has to be in the range 0 to 1 in the X axis and there are no enforced limits on the Y axis. For performance reasons, Bezier points support slopes, but not the slope weight.




Uses a single curve to modify the values. See Particle Editor for more information about Curve Editor.


This option allows child particles to inherit their parent's Field output.

Spawn Only

When a particle is born, it inherits the parent component's Field output.

Time-Based Modifiers Common Settings

Many of the Particle Effect Modifiers are time-based. This allows the modifier to accept not only the input from the property value modified by previous modifiers, but also other aspects of the particle. All of these modifiers have a common set of properties.

The easiest way to differentiate a regular modifier from a time-based modifier is that in the case of a time-based modifier, a new dropdown box appears in the user interface allowing users to select the domain input.




Following domain options are available under the  (domain) dropdown menu:

  • Age - This is the normalized time of the current particle; meaning this value will always be between 0 and 1. When a particle is initially created, Self time starts at 0 and as the particle ages, this value will progressively move toward 1 until the particle dies.
  • Spawn Fraction - When particles are spawned using the Spawn feature, a Spawn Fraction field is added to each particle property. The first particle spawned gets order value 0 and the last spawned particle gets order value 1.
  • Spawn Id - When this domain is selected, a new field called Id Modulus appears. Spawn Id specifies how many times a particle is distributed along the domain before wrapping. Just like Spawn Fraction, it generates domain values between 0 and 1, increasing with particle count. The only difference is that Spawn Fraction works only with emitters with a finite particle count and goes from 0 to 1 only once, whereas Spawn Id works with finite or infinite particle counts and goes from 0 to 1 multiple times, wrapping after Modulus entries.
  • Speed - Specifies the speed of the particle in meters per second.
  • Field - Particles can have other fields besides Size or Opacity. This mode allows users to select/choose any of the fields for a given particle. For more information about fields, please see Field in the Particle Effect Features section.
  • Attribute - Reads the value from any Attributes of the emitter. This is one of the most important domain options since it allows attributes to actually control different aspects of the effect.
  • Level Time - Specifies the time of the current level in seconds.
  • View Angle - This option corresponds to the relative angle to the camera for particles which have 3D angles. For more information about angles, please see the Angles in the Particle Effect Features section.
    When a particle faces the camera, it emits an output value of 1. When the particle is perfectly flat relative to the camera, then it emits an output value of 0. This option is best used in conjunction with the Field: Opacity feature option to avoid certain types of visual artifacts with free facing particles. For more information about opacity, please see the Field sectionon the Particle Effect Features page.
  • Camera Distance - Specifies the distance of the particle relative to the camera.
  • Random - Will always output a random value between 0 and 1. Can be used to create more sophisticated random variation effects than the Random modifier.

For immortal particles or properties that are not applied to particles during runtime, those values will always be 0.

Attribute Name

Valid when the domain is set to Attribute. This will be the name of the attribute to read from. If the attribute does not exist in this emitter, the domain will get a value of 1.


When the domain input is set to either Field or Parent Field, this option becomes available. It allows users to select/choose which field to read from:

  • Angle2D - Current particle's rotation angle (see Angles for more detail).
  • Spin2D - Current particle's spin rate (see Angles for more detail).
  • Alpha - Specifies particle's opacity (see Field for more detail).
  • Size - Specifies particle's size in meters (see Field for more detail).
  • Gravity - Specifies particle's gravity multiplier (see Motion for more detail).
  • Drag - Specifies particle's drag (see Motion for more detail).
  • Life Time - Specifies the lifetime of a particle in seconds; set it to 0 for immortal particles (see Life for more detail).
  • Random - Each particle can get a random number from 0 to 1. Use this to add variance to the behavior of each particle.


There is a difference between the Domain → Random and the Random option which is available if the Field domain is selected. Domain → Random will always output a different number and is fully stochastic. Field → Random, on other hand, corresponds to a particle's own random number and can be used to have consistent behavior between modifiers. This can be used for example to have varying but consistent size and opacity or to have all children particles share the same randomness as their parent.

Field menu options


Specifies from where the domain or the Field selection should be taken from:

  • Self - Takes the information from the particle itself.
  • Parent - Takes the information from the parent particle.

When the owner is a parent, but the particle's parent is already dead, then the domain will always be 1. The exception to this rule is the Speed feature, which will be set to 0 instead.

Domain Scale and Domain Bias

Allows the domain input to be scaled and biased. Usually useful when the input might not be in the 0 to 1 range, such as Speed or Attribute.

Spawn Only

In some cases it is desirable to choose if the Modifier is to be applied for every particle every frame or if the Modifier should only be applied once when the particle is born.

GPU Support

Currently, modifiers have a very limited support in the current GPU pipeline. At the moment, the only modifier that can be used is the Curve modifier; and it can be used only with Owner: Self as the domain.

On This Page

Table of Contents