- This line was added.
- This line was removed.
- Formatting was changed.
The Component category contains features which dynamically manipulate the component behavior as opposed to individual particles in that component. With this feature, particles can be activated based on certain conditions and probabilities.
To fully understand this category, it is recommended to study the difference between Component, Feature, Runtime and Emitter concepts on the Key Concepts section.
This feature specifies if a Runtime can spawn new particles based on an Attribute Value.
Enables the option to add an Attribute that specifies a condition needed for the particles to be activated. Any attribute can be used, but it is recommended to use Boolean attributes.
Allows a component to be randomly activated.
Defines how frequently a particle effect can be activated.
Groups multiple components together, which can be activated or ignored as a group.
If the Group value is greater than 0, then all components with the same Group value will be activated together,with one random generation. Otherwise, each component with the Group value set to 0 is activated with an independent random generation.
It appears when the Group option is enabled. Lets the components in a group to be activated separately. A component is activated only if the randomly generated number is between Selection Start and Selection Start + Probability value.
This feature specifies if a Runtime should be instantiated based on the current particle quality settings of the platform type. Use this feature to create different variations of the same Component for different platforms and quality settings.
Specifies if this Component is to be active on a PC platform.
Minimum and Maximum
Specifies the minimum and maximum quality settings allowed for this Component to be active. This option is visible only when the PC option is enabled.
Specifies if this Component is to be active on an XBox One platform.
Specifies if this Component is to be active on a PlayStation 4 platform.
This feature specifies if a Runtime should be instantiated for this component during emitter creation, based on an attribute value.
Enables the option to add an attribute that specifies a condition needed for a particle to be activated. This attribute has to be set before the emitter starts updating as EnableIf is only evaluated during instantiation. Any attribute can be used, but it is recommended to use Boolean attributes.
The main difference between EnableIf and SpawnIf is that ActivateIf is evaluated during instantiation of the Emitter and will not create the Runtime. This saves on resources, but does not allow changing the condition dynamically. ActivateIf, on the other hand, will create a Runtime regardless of the condition. This makes ActivateIf a dynamic feature.
On This Page
|Table of Contents|