This operation optimizes scene performance by replacing actors using identical meshes and material configurations with instanced versions. This reduces draw calls and improves rendering efficiency.

Usage Guidelines

• Dependencies: Run after Hierarchy Merge and Replace Duplicates to ensure all potential instances are captured.
• Instancing Logic: Identical meshes exceeding the user-defined threshold are replaced with Instanced Static Meshes (ISM) or Hierarchical Instanced Static Meshes (HISM), depending on scene complexity.
• Project Scale: For large scenes, apply this operation per level to manage memory usage effectively.
• Performance Impact: The instancing process may temporarily increase CPU and memory usage. Ensure sufficient system resources or split processing across levels if needed.

<aside> 💡

See how to apply this operation using the Palatial Editor Interface

</aside>

Best Practices

• Minimum Instances: Adjust the MinimumInstances setting to control how many identical meshes must exist before instancing occurs. A higher value is better for dense scenes like forests or cities.
• Optimize Repeated Assets: Use to consolidate repeated props, decorations, or architectural elements, reducing draw calls and boosting performance.
• Manual Review: Review the scene after processing to ensure no essential actors were incorrectly instanced. The operation changes the mesh representation but retains the original actor locations.