Specify the packed objects to extract. If this is empty, the node extracts all prims. Usually you will click the Select button to the right of the text box to select objects visually in the viewport.

When this is on (the default), the original USD packed prims are not passed though to the output.

How to find the USD prims to extract.

Whether to output the extracted USD prims as a new USD packed primitive, or as Houdini polygonal geometry.

Performs additional levels of unpacking after the initial Traversal. For example, this can be useful for unpacking point instancers all the way to polygonal geometry, since a single iteration of unpacking produces a packed USD primitive for each instance.

When this parameter is disabled, the packed USD primitives are unpacked as far as possible.

Specifies whether to place the packed primitive’s point at the origin of its coordinate frame, or at the center of its bounding box.

If enabled, creates a SOP primitive attribute containing the scene graph path of the original USD primitive.

If enabled, creates a SOP primitive attribute containing the name of the original USD primitive.

If enabled, creates a SOP primitive attribute containing the file path (or LOP node path) of the original USD primitive’s stage.

If enabled, creates a SOP primitive attribute containing the number of point instancers that were unpacked to produce the primitive.

When unpacking to regular Houdini geometry, this is a list of patterns matching existing Houdini geometry attributes (not USD attributes) on the USD Packed Primitive that should be transferred onto the output geometry. For example, you might have sent the USD packed primitives through an RBD simulation in Houdini, which wrote position and rotation attributes onto the packed prims, which you want to transfer onto the extracted geometry.

When unpacking to regular Houdini geometry, this is a list of patterns matching existing Houdini geometry groups on the USD Packed Primitive that should be transferred onto the output geometry.

When unpacking to regular Houdini geometry, this is a list of patterns matching USD primvars that should be converted to Houdini geometry attributes.

Includes primvars that are inherited from parent primitives when unpacking to regular Houdini geometry. The Import Primvars filter is also applied to select which inherited primvars are imported.

If the visibility attribute is authored on the USD prim, a usdvisibility SOP attribute is created with its value (invisible or inherited). When this option is enabled, the usdvisibility attribute will instead contain the computed visibility for every prim. This can be useful to determine which primitives are visible, but should be used with caution when round-tripping to avoid replacing the original USD visibility attributes.

When unpacking to regular Houdini geometry, this is a list of patterns matching USD attributes that should be converted to Houdini geometry attributes (in addition to the primvars specified in Import primvars).

These patterns are only matched against custom USD attributes on the prim being imported. USD attributes that are part of a schema have special handling (for example, the faceVertexIndices attribute on a mesh primitive is converted into the topology of the resulting polygons).

Unlike primvars, custom attributes do not specify an interpolation mode. If the attribute’s value is an array, the node guesses the Houdini attribute level (point, vertex, primitive, or detail) based on the number of elements in the array.

Since only primvars can be inherited from parent primitives, the Import Inherited Primvars option does not apply for custom USD attributes.

When unpacking to regular Houdini geometry, this is a list of patterns matching USD primvars that should be converted to non-transforming Houdini geometry attributes.

USD generally stores texture coordinates in a primvar named st, while Houdini stores them in an attribute named uv. When this is on, the node automatically converts USD st primvars to uv attributes.