Instanceable Blueprints

Species support spawning blueprints, but this is sub-optimal in terms of performance and memory usage. Instead, we recommend spawning the contents of the blueprint as instances. Blueprints spawn this way are as efficient as normal mesh instances.

1. To use this feature, first create a new blueprint. Use BiomesInstanceableBlueprintBase as the parent class for your blueprint.

2. Then add a few meshes in the blueprint.

3. Pick that blueprint as an asset in some Species (the same way you pick meshes).

4. And regenerate the world. The contents of the blueprint should spawn as instances.

You can also add a BiomesInstanceableBlueprint interface to existing blueprints to make them work the same way. Enter Class Settings→Interfaces→Add to pick the interface.

note

Spawning larger blueprints requires increasing Priority Radius in Species to prevent various species from overlapping.

We recommend spawning objects of similar size within one Species so that they could work well with the same Priority Radius.

Nesting

Instanceable blueprints can be put inside each other by using the Child Actor Component to combine into larger structures and allow larger blueprint reuse.

Make sure to avoid circular dependencies.

Non-mesh components

You can spawn any type of component in an instance-able blueprint but only meshes have in-engine optimizations for instancing. Other components will be spawned in actors with similar performance characteristics as if they were placed by hand.

Components are spawned into shared actors not as individual actors.

This should be considered when writing custom logic in your components.

Biomes Instances Settings

You can set Instance Settings for the component in the blueprint that will override ones from the Species asset for that component.

For that, you need to use BiomesStaticMeshComponentWithSpawningInfo. In which you can find Instances Settings parameters.