Choose whether to copy a specific node’s parameters into a dictionary attribute on the detail (whole geometry), or build a geometry representation of the nodes in a subnet.

The Points methods replace the input with the generated points (they do not pass through the geometry in the input).

The node to read parameters from.

This creates a dependency on the target node’s parameters, but not on the data of the node itself. Editing a node’s parameter interface does not trigger dependencies, so creating or removing spare parameters on the target node will not recook this node.

The node type categories (for example, SOP, VOP) that can be encoded as points. This can be a space-separated list of names. The default is *, meaning all categories.

The name of the dictionary attribute to create and fill in with parameter data. When Method is set to Detail from Single Node, this is a detail attribute. Otherwise, this is a point attribute on the points created to represent nodes.

Only store the values of parameters whose internal names match these names/patterns. This can be a space-separated list of names and/or patterns. The default is *, meaning store all parameters. Note that multiparm instances are only included if they and the parent multiparm folders both match.

When turn off, the node stores a multiparm folder as a single item, where the value is a list of the multiparm instances. When turned on, the node stores multiparms as separate keys (for example, it would store a multiparm named value with three instances as separate value1, value2, and value3 keys). By default, this parameter is turned off.

Similar to Flatten Multiparms, but for ramp parameters.

This parameter is only available if Flatten Multiparms is turned off.

Parameters that contain expressions are normally evaluated at the current time and the current values stored. However, it might not be possible or sensible to evaluate them outside the node’s cooking. Turning this off will store the values of constants but not evaluate expressions.

If the node is a locked SOP node, the geometry is packed and attached to the generated point.

Often there is implicit wiring in a graph. Spare inputs, block paths, and subnetwork outputs are all controlled by parameters or flags rather than actual inputs. Turning this on will cause polylines representing those implicit wires to be made explicit. Explicit wires better survive geometry operations as they are not sensitive to duplicate names or renaming of points.

When turned on, each input/output of the specified network or node will have an extra point created of type “null”. These new points will be added to the “inputs” and “outputs” point groups, which make it easier to compose multiple networks, as the inputs/outputs are distinct, simple, and well-defined. It also makes Invoke Graph easier to use, as the inputs and outputs are already registered.

When turned on, will create channel primitives from any animated parameters, adding them to the geometry. This only applies if Method is one of the Points methods, and Evaluate Parameters is turned off.

The generated geometry records the location of all nodes, but this is irrelevant to how the network acts when invoked. Only when Update on Node Movement is turned on is the geometry recomputed when nodes move. This prevents unwanted recooks generated by node movement.

The generated geometry records the name of all nodes, but this is irrelevant to how the network acts when invoked. Only when Update on Node Renaming is turned on is the geometry recomputed when nodes are renamed. This prevents unwanted recooks generated by node renaming.