← Commit history

publish all feature sub-readmes + images to the page repo (canonical git store)

John Lauer ·32ae0932af ·2mo ago ·parent 0e1c398
5 files changed +24−9
docs/3d-viewer-and-export.md+20−5
@@ -83,11 +83,26 @@ The pattern: Because it is name-driven, it survives a re-import of an updated STEP: the same rules recolor the new geometry without hand-picking bodies in the UI. -> **Referenced example, not yet documented here.** Drew posted a before/after in Google Chat showing-> exactly this on the Essemtec machine, a grey STEP turned into a colored assembly. I could not-> locate that post while writing this (searched Workcell, Hydrogen, Workcell Vision System and the-> other active spaces for "essemtec", "coloriz*" and today's 3D messages, no match). If you point me-> at it, the before/after images belong right here as the worked example.+### Worked example: the Essemtec pick-and-place++Drew ran this on the Essemtec machine. The STEP arrived as one undifferentiated grey solid, every+body the same colour, so the shrouds, frame, interior and rails were indistinguishable.++**Before.** The imported STEP: a single grey mass. You can barely tell the enclosure from the base.++![Essemtec STEP as imported, one flat grey solid](docs/img/step-colorize-before.png)++**After.** Name-driven appearances applied per occurrence: white shrouds, black base and frame, a+dark interior that now reads as depth, and the red rail picked out.++![The same STEP after per-occurrence colorization](docs/img/step-colorize-after.png)++Same geometry in both. Nothing was remodelled: only appearance was assigned per occurrence. The+second one reads as a machine, which is what makes it usable as a viewer asset, a wiki hero, or a+diagram someone can point at.++Because the rules match on component names, they survive a re-import. Drop in an updated STEP from+the vendor and the same script recolours the new geometry without hand-picking bodies in the UI.  ## Library 3D packages 
docs/fusion-mcp-server.md+1−1
@@ -45,7 +45,7 @@ which opens Preferences, expands General, selects API, ticks `Fusion MCP Server (runs locally on this device)`, clicks Apply then OK, and verifies the port is listening before reporting success. -![The API page with the MCP server toggle](prefs-3-api-mcp.png)+![The API page with the MCP server toggle](docs/img/prefs-3-api-mcp.png)  > ⛔ **The setting is discarded unless Apply is clicked.** Restarting or killing Fusion with the > dialog open reverts it, and the port stays closed while the checkbox looked right. This cost a
docs/fusion-preferences.md+3−3
@@ -46,16 +46,16 @@ hands you a screenshot to click rather than pretending control names exist.  **1. Preferences opens on General.** Note the collapse arrow beside "General". -![Preferences open on the General page](img/prefs-1-open.png)+![Preferences open on the General page](docs/img/prefs-1-open.png)  **2. General expanded.** API, Design, Manufacture, Electronics, Render, Drawing and Simulation appear. None of these are in the UIA tree. -![General expanded to reveal API](img/prefs-2-general-expanded.png)+![General expanded to reveal API](docs/img/prefs-2-general-expanded.png)  **3. The API page**, with `Fusion MCP Server (runs locally on this device)` and its port, 27182. -![The API page with the MCP server toggle](img/prefs-3-api-mcp.png)+![The API page with the MCP server toggle](docs/img/prefs-3-api-mcp.png)  ## Using it 
docs/img/step-colorize-after.pngadded
⋯ 1 unchanged line ⋯
docs/img/step-colorize-before.pngadded
⋯ 1 unchanged line ⋯