Troubleshooting

This page lists common InstanceForge issues and the first checks to make.

Empty scan

If Scan returns 0 ready candidates or 0 groups, check these items first:

• scan scope;
• selected actors or current level contents;
• Required Tag spelling;
• Exclude Tags;
• Include StaticMeshActors;
• Include StaticMeshComponents inside Blueprint actors.

Skipped items usually mean filters excluded them.

Common causes

Delete and restore safety

Do not use Delete safe originals after backup as the first test pass.

Safe cleanup rule:

1. Build with Hide originals after build.
2. Verify generated instances visually.
3. Confirm build history exists in Build History and Restore.
4. Test restore on a safe sample.
5. Rebuild with Delete safe originals after backup only after restore is validated.

Originals are still visible after build

Check Original Handling in Plan and Build.

Draw Calls says Run Scan first

Run Scan Sources before reading Build Plan or Benchmark draw-call estimates.

The draw-call values are based on the current Build Plan.

Build button is not safe to click

Do not build if:

• enabled group count is wrong;
• instance count is wrong;
• Original Handling is not what you intended;
• preflight reports hard errors;
• the scene is not backed up or under source control.

Benchmark has spikes

Benchmark is collected inside the editor.

For more stable readings:

• keep the viewport still;
• wait for shaders and asset loading;
• avoid moving the camera;
• compare Median and P95, not only Avg Frame;
• repeat capture if results are close.

Restore is unavailable

Restore can be unavailable when:

• the selected record is already rolled back;
• the selected record is partial or failed;
• no active build record is selected;
• the build history actor is missing;
• deleted source data is insufficient for recreate.

Use the selected build summary to inspect restore availability.