| Since | 22.0 |
This node allows the use of a SOP dive target to create APEX rigs using tools like the Autorig Builder and APEX AutoRig Component SOPs. The Shape Primitives are converted to geometry in a packed folder structure, and this geometry is the dive target’s input geometry. The Shape Primitives are bound to the rig’s inputs and deformed by the rig’s outputs. SOP attributes that are added to the shapes during the rigging process, such as the
boneCapture attribute, can be authored as an overlay on the USD primitives.
See animating in LOPs for an example of how to use this node.
Parameters ¶
Character Primitive
The primitive path that represents the character (typically this is the asset’s root primitive).
The HoudiniApexCharacterAPI schema is applied to this primitive, which references the rig and binds the Shape Primitives to the rig’s inputs and outputs.
Shape Primitives
The pattern specifying the primitives under the Character Primitive to convert to geometry and add to the packed folder structure for the SOP dive target’s input geometry. The packed folder paths are named based on the relative path to the Character Primitive. The Character Primitive configures bindings for these primitives to the character’s rig inputs and outputs.
The default pattern includes all the geometry primitives.
Adjusts the packed folder paths for the imported Shape Primitives in the SOP dive target. This can be useful if, for example, you have an existing rig that expects the shapes to have different names.
When a multiparm entry is turned on, the renaming filter is active.
From
The string pattern to rename.
This uses the same pattern format as Attribute String Edit.
To
The replacement pattern for the string.
This uses the same pattern format as Attribute String Edit.
Rig Save Path
When turned on, configures the save path for the rig data.
When you write out USD using a USD Render ROP, the geometry is saved to a
.bgeo.sc file using this file path (after output processing).
When turned off, the save path is automatically determined based on the node name.
Controls which attributes are authored as an overlay on the Shape Primitives.
This should only include attributes added during the rigging process, such as boneCapture.
Enable Attributes
When turned on, the Attributes setting is used when translating the SOP geometry to USD.
Otherwise, the parameter’s default value is used unless a usdconfigattribs detail attribute exists on the SOP geometry (for example, from the USD Configure SOP).
Attributes
A space-separated list of attribute names/patterns specifying the SOP attributes to import into USD as primvars.
In addition to matching attribute names directly, there are some values with special meanings:
bounds
Authors the USD extent attribute using the calculated bounding box of the associated SOP geometry.
visibility
Authors the USD visibility attribute based on the value of the usdvisibility geometry attribute.
type:string
Matches against any SOP string attributes.
type:uv
Matches against any SOP texture coordinate attributes.
See importing attributes for information on how the importer converts certain well-known Houdini attributes to their USD equivalents.
Enable Indexed Attributes
When turned on, the Indexed Attributes setting is used when translating the SOP geometry to USD.
Otherwise, the parameter’s default value is used unless a usdconfigindexattribs detail attribute exists on the SOP geometry (for example, from the USD Configure SOP).
Indexed Attributes
A space-separated list of attribute names/patterns specifying the SOP attributes to import into USD as indexed primvars.
If a SOP attribute matches this pattern, the importer authors the primvar as an indexed array of values (that is, an array of values called primvars:‹name›, and an array of indices into those values called primvars:‹name›:indices).
Preparing an indexed primvar can be expensive for attributes that are not integers or strings. You should only use indexed primvars where it is likely to result in significant savings in storage size due to a small number of unique values being used across a large number of components.
Enable Import as Single Element Array
When turned on, the Import as Single Element Array setting is used when translating the SOP geometry to USD.
Otherwise, the parameter’s default value is used unless a usdconfigconstantattribs detail attribute exists on the SOP geometry (for example, from the USD Configure SOP).
Import as Single Element Array
A space-separated list of attribute names/patterns specifying the SOP attributes to import into USD as primvars with Constant interpolation (an array with a single value for the whole primitive), regardless of whether the SOP geometry attribute is a point, primitive, or vertex attribute. If multiple values could be chosen for a particular USD primitive, the importer chooses the first value it encounters.
Importing as a single element array (versus Import as Single Value) can be useful since it allows the primvar’s interpolation to be overridden without changing the primvar’s type.
Enable Import as Single Value
When turned on, the Import as Single Value setting is used when translating the SOP geometry to USD.
Otherwise, the parameter’s default value is used unless a usdconfigscalarconstantattribs detail attribute exists on the SOP geometry (for example, from the USD Configure SOP).
Import as Single Value
A space-separated list of attribute names/patterns specifying the SOP attributes to import into USD as primvars with Constant interpolation and a single value for the whole primitive, regardless of whether the SOP geometry attribute is a point, primitive, or vertex attribute. If multiple values could be chosen for a particular USD primitive, the importer chooses the first value it encounters.
This is the default behavior for how detail attributes are imported.
This is similar to Import as Single Element Array, but the primvar’s type is a scalar value instead of an array with a single element (for example, vector3f instead of vector3f[]).
Enable Boolean Attributes
When turned on, the Boolean Attributes setting is used when translating the SOP geometry to USD.
Otherwise, the parameter’s default value is used unless a usdconfigboolattribs detail attribute exists on the SOP geometry (for example, from the USD Configure SOP).
Boolean Attributes
A space-separated list of attribute names/patterns specifying which integer SOP attributes should be converted to primvars of type bool.
Enable Unsigned 32-bit Attributes
When turned on, the Unsigned 32-bit Attributes setting is used when translating the SOP geometry to USD.
Otherwise, the parameter’s default value is used unless a usdconfiguintattribs detail attribute exists on the SOP geometry (for example, from the USD Configure SOP).
Unsigned 32-bit Attributes
A space-separated list of attribute names/patterns specifying which integer SOP attributes should be converted to primvars of type uint.
Enable Unsigned 64-bit Attributes
When turned on, the Unsigned 64-bit Attributes setting is used when translating the SOP geometry to USD.
Otherwise, the parameter’s default value is used unless a usdconfiguint64attribs detail attribute exists on the SOP geometry (for example, from the USD Configure SOP).
Unsigned 64-bit Attributes
A space-separated list of attribute names/patterns specifying which integer SOP attributes should be converted to primvars of type uint64.
Enable Asset Path Attributes
When enabled, the Asset Path Attributes setting is used when translating the SOP geometry to USD.
Otherwise, the parameter’s default value is used unless a usdconfigassetpathattribs detail attribute exists on the SOP geometry (for example, from the USD Configure SOP)
Asset Path Attributes
A space-separated list of attribute names/patterns specifying which string SOP attributes should be converted to primvars of type asset.
Enable USD Custom Attributes
When turned on, the USD Custom Attributes setting is used when translating the SOP geometry to USD.
Otherwise, the parameter’s default value is used unless a usdconfigcustomattribs detail attribute exists on the SOP geometry (for example, from the USD Configure SOP).
USD Custom Attributes
A space-separated list of attribute names/patterns specifying the SOP attributes to import into USD as attributes (rather than primvars).
Enable Translate UV Attribute to ST
When turned on, the Translate UV Attribute to ST setting is used when translating the SOP geometry to USD.
Otherwise, the parameter’s default value is used unless a usdconfigtranslateuvtost detail attribute exists on the SOP geometry (for example, from the USD Configure SOP).
Translate UV Attribute to ST
When turned on, converts the SOP vertex attribute uv into a USD primvar called primvars:st. Whether you need to turn this on depends on the renderer you are using and how your shaders are authored. If you are rendering with Karma, leave this off.
(As of this writing there is no strict standard for texture coordinate naming in USD, but the use of st is a common convention, whereas in SOP geometry, using uv is the common convention.)
| See also |