Volumes
InstanceForge volumes provide level-scoped include/exclude areas for scan and restore workflows.
Use volumes when a level is too large for a broad scan or when you need to control optimization by area.
Volume classes
InstanceForge provides these runtime volume classes:
AInstanceForgeBoxVolumeAInstanceForgeSphereVolume
Both derive from AInstanceForgeVolumeBase.
They live in the runtime module so they can be placed and saved in maps.
Volume properties
| Property | Purpose |
|---|---|
bEnabled | Controls whether the volume participates when enabled-volume filtering is used. |
Mode | Include adds candidates. Exclude removes candidates inside the volume. |
RequiredTagOverride | Optional required tag override for candidates matched by this include volume. |
InstanceTypeOverride | Stores target intent for volume workflows. |
bIncludeStaticMeshActors | Allows or disallows AStaticMeshActor candidates for this volume. |
bIncludeBlueprintComponents | Allows or disallows UStaticMeshComponent candidates inside Blueprint actors for this volume. |
Scan with volumes
- Place InstanceForge volumes in the level.
- Configure include/exclude modes.
- Open
Tools > InstanceForge. - Open
Scan. - Choose
InstanceForge Volumesas the scan scope. - Click
Scan Sources.
Restore with volumes
The Instances tab includes volume restore actions.
Use them to restore generated components or instances affected by selected volumes.
| Action | Purpose |
|---|---|
Restore Volume Components | Restores generated components touched by selected volumes. |
Restore Volume Instances | Restores generated instances inside selected volumes. |
Containment behavior
The scanner uses component origin point containment for volume inclusion.
Bounds-overlap and full-bounds workflows should be treated as future behavior unless exposed in your current build.
Safety
Volume scanning is still a controlled selection workflow.
Review the Build Plan before building and use Hide originals after build for the first pass.