|On this page|
Since Houdini 18.5, SOP geometry supports dictionary attributes. This node fills in a dictionary attribute on the detail with parameter values from a certain node. You can use this to record the settings of a node so later operations can see how the geometry was constructed.
You can also use this node to convert node graphs into geometry, storing the individual node parameters and wiring as attributes.
Tips and notes
The node always grabs the parameter values at the current time.
Choose whether to copy a specific node’s parameters into a dictionary attribute on the detail, or build a geometry representation of the nodes in a subnet.
Create a dictionary attribute on the detail (whole geometry) containing a specified node’s parameters.
Outputs a set of points encoding the nodes in a node graph as points and their parameters/wiring as attributes on the points.
Like Subnetwork, but the target node should be the end node of a compiled block. This node will automatically encode all nodes that belong to the compiled block.
The Subnetwork and Compiled Block methods both 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.
What node type categories (for example,
VOP) 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 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 matches 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 match and the parent multiparm folder also matches.
When this is off, the node stores a multiparm folder as a single item, where the value is a list of the multiparm instances. When this is on, the node stores multiparms as separate keys (for example, it would store a multiparm named
value with three instances as separate
value3 keys). The default is off.
The encoding choices as Flatten Multiparm but for ramp parameters.