Section 5. Actor and Component Pooling
Section 5.1. Introduction
rdInst can efficiently pool your actors and components for fast instantiation at runtime. You can choose how many to Pool, and if they should be created initially or on-demand.
You can do this from an rdActor or using the rdInst Subsystem, for the Component Pooling – it must be done from rdActor.
Section 5.2. Actor Pooling from rdActor
rdActor itself does not contain routines for pooling actors as it makes more sense to do that from the singleton.
It does have events that get fired when an actor is Pooled or Depooled, and you can override them in the rdActor to do any setup and reset work you require.
Section 5.3. Component Pooling from rdActor
You can Pool any type and any amount of components using the rdInst Component Pooling routines.
Note that some components (such as the Niagara Component) have their own pooling, so it pays to check first.
Check out Tutorial 14 for an example of Component Pooling, and check the rdActor Pooling section of the Reference Manual.
Section 5.4. Actor Pooling from the BaseActor or Subsystem
Use these routines to Pool your Actors in the most efficient way.
Check out the tutorials below for examples on how to use it, and check the rdInstBase Pooling section of the Reference Manual.
Section 5.5. Pooling Tutorials
To find out how to implement Actor and Component Pooling you can read these tutorials:
Tutorial 14 – Component Pooling
Tutorial 17 – Pooled Actor Movement