Part Authoring

Overview

Creates or updates a reusable part (.pxnpart). Register an asset built in the graph as a categorized and tagged library package, ready for arrangement in part_composer. This is the writing side of the asset library.

Usage tips

• Choose between two save types: snapshot fixes the image, while parameterized retains exposed parameters that can be adjusted at placement time. Use a parameterized part when colors or variations should change during layout.
• Save explicitly from the Inspector; parts are not collected automatically.
• For a temporary handoff, live sync from a regular node is sufficient.

Related nodes

• part_composer — uses the parts
• save_map_asset — a similar library for map images
• bake_subgraph — fixes a result inside a project without packaging it

Creates or updates a .pxnpart package for Part Composer.

Uses

• Place a part_node in the graph, distinct from regular and custom nodes
• Save a .pxnpart from an internal graph and its output image
• Store category and tags as .pxnpart metadata for searching and filtering in Part Composer
• Create snapshot and parameterized .pxnpart files
• Update the linked file when the node is associated with an existing .pxnpart

Remarks

Part Composer does not automatically collect project-local part_node instances. To use one as a formal reusable part, save or update it as .pxnpart from the Inspector.

Snapshot and parameterized parts share the .pxnpart extension. _snapshot or _parameterized is appended to the filename automatically.

To send the current output of a node temporarily to Part Composer within the project, use "Expose to Part Composer via live sync" on a regular node. This is a temporary feature separate from .pxnpart packages.