Vis Automations · In-app tool, Automation Scripts menu

Model Inspector

A Python tool that Vis lists in its own Automation Scripts menu: it attaches to the open session, reads every part, selects the largest, retitles the view, adds a snapshot and writes a report.

Verification NOT fully passing on Vis 2606.0 build 26134 + 2606.2610 · 2026-10-29 · repo tc-vis-automation 9f1b0af · The tool, the menu launch and restart persistence work; registration by registry does not.

Model Inspector’s capture: the largest part, Case_r:123-200, in the selection highlight. Click to zoom.
Vis runs the menu entry with ShellExecute; the script attaches back to the same Vis session over COM.

What was asked

Show that a tool can live inside Vis, launched from Vis itself and working on the model the user already has open, rather than only as an outside script that starts its own Vis.

What it does

  • Reads the physical properties of every part in the open model.
  • Selects the largest part, drawn in the selection highlight.
  • Retitles the view, so the window title names the largest part.
  • Adds a named snapshot and captures the view.
  • Writes an HTML report and a JSON run log to Documents\VisModelInspector and opens the report.
7/8
checks hold; the one that fails is registration through the registry
1
Vis process before and after: it works in your session
67
parts read on the engine example

Works: adding the script once through Manage Scripts, launching it from the menu, and the entry staying after Vis restarts. Does not work: registering it by writing the registry. See Open questions.