At a glance
- Compare 3D polygon counts, 2D plan performance or 3D loading diagnostics.
- Search and group the results, then select or locate the corresponding model elements.
- Export the filtered results and repeat the analysis after model changes.
Analysis mode and scopeChoose what to measure before reading the rankings.
For a polygon analysis, use the current 3D model or selected elements. A view-based analysis reflects the model visibility and cuts in that view; elements outside that scope are not represented by the same result.
2D plan performance compares repeated element reads on the current storey. This measures a different kind of work from the 3D polygon analysis. 3D loading diagnostics measures repeated access to each element’s 3D geometry. Its individual timings remain separate from any whole-view rebuild and redraw measurements. These modes help locate contributors; they do not measure file size or graphics-card performance directly.
Results, filters and groupingUse the results to identify the main contributors.
Sort or search the captured results, or group them to compare related elements. Select a result to select or zoom to the corresponding element in the project.
Primitive counts and median read timings describe different things. A repeated library part may be easier to assess as a group, while an individual high-count element may warrant inspection on its own.
Refreshing and exporting resultsThe results describe the scope captured by that analysis.
Run the analysis again after changing the model. Export includes the filtered results across all pages, rather than only the page currently shown.
Do not add individual read timings together and treat them as a predicted view-loading time. Cached reads also differ from a fresh load. Use the results to locate contributors and compare changes, rather than as a guaranteed load-time forecast.