Appearance
Object and Boolean colours
Assign colours to objects and surviving Boolean-source surfaces, then verify the same regions in a freshly generated export.
- Where to find it
- Object colour action in Designer / Project Browser
- When to use it
- Colouring primitive and nested Boolean geometry
On this page
Step by step
- Assign the intended colour to the object or Boolean source.
- Move the pointer off the object and inspect it in a shaded view; hover and selection highlights are temporary.
- Save, reopen and check that the intended colours persist.
- Regenerate the Python/component export after the change.
- Place a fresh instance and check every coloured region, surrounding geometry and ports.
Designer and Plant are separate checks
Correct Designer colours and a setColor call in generated Python do not by themselves prove the final native appearance. Later boolean operations can affect colour ownership.
Recent colour-region handling
Differing-colour union regions can remain separate native solids. This is not fused ACIS per-face colouring. Verify the resulting colours and geometry in your Plant host.
Acceptance scope
Check overlapping or coplanar boundaries and cuts that remove an entire colour region in your Plant host. If only one object or colour appears, save the generated JSON/Python and diagnostics when reporting the issue.
Keep in mind
- Do not reuse an old generated Python file to test an updated exporter.
Documentation reviewed