Smart Auto

Smart Auto

Smart Auto is the recommended way to choose generated instance layouts in InstanceForge.

It follows a practical rule: prefer ISM first, use Split ISM before HISM, and choose HISM only when it clearly wins.

Smart Auto settings

Use this setup for normal production work:

Target: Auto
Auto Strategy: Smart Prefer ISM
Smart Auto Preset: Balanced
Original Handling: Hide originals after build

Balanced is the recommended default.

Simple Threshold vs Smart Prefer ISM

StrategyBehavior
Simple ThresholdChooses HISM when the group count is greater than or equal to the threshold. Otherwise chooses ISM.
Smart Prefer ISMScores Single ISM, Split ISM, and HISM using group metadata and tuning settings.

Smart Prefer ISM is usually better for mixed production scenes because it avoids blindly converting every large group to HISM.

What Smart Auto can choose

ResultMeaning
Single ISMOne ISM component for a compact/simple group.
Split ISMMultiple ISM components split by spatial clusters.
HISMOne HISM component when HISM wins clearly.

Reading decisions

Smart Auto decision reason

Look at the selected group row in the Build Plan.

Check:

  • instance count;
  • resolved target;
  • draw-call impact;
  • tooltip or diagnostic reason;
  • Smart Auto preset and margin.

Use these diagnostics before forcing manual overrides.

Scoring inputs

Smart Auto can consider metadata such as:

  • instance count;
  • material slot count;
  • mobility;
  • spatial spread;
  • split cluster count;
  • LOD count and LOD0 triangle/vertex data when available;
  • collision and shadow signals;
  • Nanite or LOD screen-size related data when available.

When metadata is missing, Smart Auto uses conservative fallbacks and surfaces hints.

Presets

PresetHISM Win MarginUse case
Conservative35%Strongly prefers ISM/Split ISM.
Balanced25%Recommended default.
Aggressive15%More willing to choose HISM.
CustomUser-definedUsed when you edit the margin manually.

HISM Win Margin % controls how much better HISM must score compared with the best ISM path.

Important settings

SettingPurpose
HISM Fallback CountUses HISM when Split ISM is not practical for very large groups.
Allow Spatial Split ISMAllows distributed groups to become multiple compact ISM clusters.
Cluster RadiusControls spatial cluster size for Split ISM.
Min Instances/ClusterPrevents tiny clusters.
Max Clusters/GroupPrevents too many generated components.
HISM Win Margin %Required HISM score advantage over the best ISM path.

Typical examples

Scene patternCommon result
Small compact groupSingle ISM
Large distributed groupSplit ISM
Large static heavy groupHISM if margin passes
Movable groupUsually ISM or Split ISM unless manually forced

Manual overrides

Use manual overrides only when you understand why the automatic decision is not suitable.

Manual HISM on movable groups can produce warnings.

Next steps

Continue to Plan and Build or Configuration Reference.