Troubleshooting

Common Issues

The scan is taking a very long time.

The scanner might be analyzing massive third-party packages or large asset libraries.

• Solution: Ensure your scenes are located in the Assets folder. The scanner ignores the Library and Packages folders to stay fast.

Settings asset not found.

This happens if the AnalysisSettings file was deleted or moved.

• Solution: Go to the System Setup tab in the Main Dashboard and click “INITIAL SETUP REQUIRED”. This will regenerate the settings file.

Memory values show as 0.

Unity’s internal memory profiling requires the Editor to be in Play Mode to provide accurate Reserved/Allocated values.

• Solution: Enter Play Mode before checking the memory metrics in the dashboard footer.

Heatmap is not rendering.

The heatmap only renders in the active Scene View tab.

• Solution: Ensure a Scene View is open and focused.

Error Codes

• Exit Code 1 (Headless): Indicates a “Performance Threshold Breach” during a CI scan. Your scene is too heavy!
• Scan Error [IndexOutOfRange]: This usually indicates a corrupt scene file or a missing asset reference within a scene.