Skip to end of metadata
Go to start of metadata

Overview

Second Generation particles (SecondGen) permits individual particles to act as sub-emitters of other components. Many different types of effects can be achieved with this feature, but the most common ones would be effects with trails. Although the feature is called SecondGen which implies a parent/child relationship, in practice there is no limit to the number of generations that can be achieved. There is also no limit on the number of SecondGen features that can be added to a single Component or the number of child components attached to those features.

The following options are available under the SecondGen category:  

OnCollide

This feature will be triggered every time a parent particle collides. Can be triggered several times per parent and it will be valid until the parent dies.

For more information regarding the options available in this feature, see the Common Settings section below.

OnDeath

This feature will be triggered every time a parent particle dies. This is a single frame event, meaning that it will only allow child particles to spawn in a single update loop.

For more information on the options available in this feature, see the Common Settings section below.

OnSpawn

This feature will start spawning child effects every time a new particle is spawned. This is a continuous event which means it will activate spawning of the child particles when a new parent particle is born and will automatically stop when the parent particle finally dies. The actual child spawning logic is executed within the child component (see Spawn features for more details). Use this feature to create effects such as trails.

For more information regarding the options available in this feature, see the Common Settings section below.

Common Settings

All SecondGen features share common behavior which is then specialized, but is based on each individual feature.

PropertiesDescription
ModeWhen more than one child component is attached to this SecondGen feature, then it specifies which behavior is to be expected when the feature gets triggered for each parent particle. The following options are available:
  • All: When the trigger conditions are met, starts spawning particles on all children attached to the feature. Usually used when each child acts as a visual layer and following their parents.
  • Random: When the trigger conditions are met, randomly chooses one of the attached children to start spawning child particles. Usually used when child components are variations of each other and only one is supposed to be active for each parent particle.
ProbabilitySets the probability that a child particle will start spawning for a parent particle when the trigger condition is met. A value of 1 means it will trigger every time, a value of 0 effectively disables the feature. A value of 0.5 means that only half of the trigger conditions will actually start to spawn new child particles.
ComponentsLists the number of child components attached to this feature. This property is read only. To attach a child to a parent component use the graphical user interface links.

 

GPU Support

GPU particles can be spawned by CPU particles but not the other way round. Information about the parent particles is sent to the GPU and saved in the GPU memory.

 

  • No labels