Procedural Mesh Blueprint

Parent mesh swapping and PCG-driven child meshes

Procedural Mesh Blueprint centers on a straightforward environment workflow: drag in a static mesh, treat it as the parent, and generate child meshes onto it through PCG. The setup is aimed at adding surface detail without manual placement, so a rock, prop, or other scene object can carry overgrown elements such as moss or grass directly through the blueprint.

The blueprint supports dynamically swapping the parent mesh by drag-and-drop, which makes it useful when the same setup needs to be tested across different assets. Child mesh arrays can also be added, removed, and swapped dynamically, so the generated result is not locked to a single detail set. That keeps the tool focused on iteration rather than on building one fixed decorative arrangement.

The overall idea is simple: environment artists can attach procedural growth to a base mesh and let the system handle the placement of the child elements. The workflow is presented as artist-friendly and avoids the need to manually paint foliage on rocks or similar surfaces just to get a believable overgrown look.

Controls that shape the growth on the parent mesh

The blueprint includes parameters that control the falloff amount of the PCG-generated child meshes as well as pruning. Those controls matter because they change how dense or reduced the generated growth appears on the parent surface, giving the result a more deliberate shape instead of a uniform blanket of detail.

There are also toggles for absolute scaling of the child mesh and for inverting them on the parent mesh. In the current version, the older Invert Child Meshes Option has been removed and replaced with Vertical Mesh Amount, which makes it possible to generate additional separate child meshes along the XY axis of parent meshes. That change is aimed at cases like ivy, vines, and roots that need extra layers or runs of detail along the side of a mesh rather than only on its surface.

Parameter hover states now include short descriptions, which makes the blueprint easier to read while adjusting values. That small addition fits the rest of the workflow, which is built around quick visual iteration instead of a heavy technical setup.

Version 2, reconnect behavior, and the saved graph

The blueprint and PCG graph are saved as V2, keeping the updated setup separate from the earlier version. That means the revised blueprint exists as its own saved version rather than replacing the previous one. The update also keeps the newer parameter behavior and the revised child-mesh generation logic together in the same saved setup.

If the child mesh PCG does not function right away, it only needs to be reconnected once. After that reconnect step, it continues to work going forward. A short guide for that reconnect step is included with the blueprint guide documentation, which suggests the workflow expects a quick initial setup adjustment before everything runs smoothly.

The blueprint also includes the ability to break the PCG link and separate the parent and child meshes, along with their associated materials, so the result can be converted to static meshes. That makes the setup useful not only for procedural placement, but also for turning the generated arrangement into a more permanent asset state when needed.

What the package is set up to handle in a scene

This blueprint is a strong fit for overgrown environment work where static meshes need quick procedural dressing. The clearest examples are rocks covered with moss or grass, but the same system also supports ivy, vines, and roots running along a parent mesh. Those are the kinds of details that usually take time to place by hand, especially when the same treatment needs to be repeated across multiple assets in a scene.

The required plugins are PCG And PCGGeometryScriptInterop, which must be enabled for the blueprint to function. The setup also comes with sample meshes and associated textures, and those placeholders account for the nearly 1.8GB file size. They are only there to show what the blueprint can do visually, and they can be removed once your own assets are swapped in.

What stands out here is the focus on practical scene dressing rather than broad procedural complexity. It is built for environment artists who want to drop in a mesh, generate overgrown child details, adjust the result through a few targeted controls, and then either keep it procedural or break it into static meshes when the scene calls for it.

Visual Breakdown