The scene graph path at which to create the point instancer prim (when Method is “Point instancer”), or the parent of all created prims (when Method is anything other than “Point Instancer”).

If the prim at Primitive path doesn’t exist, this node creates it. If it creates the prim, it sets this as the prim’s kind.

See Instancing in USD for more information.

Compute the extents (bounding box) of the instanced geometry and store this on the instancer prim.

Where to get the points to copy onto.

When Location source is “External SOP”, the node path of the SOP node that generates the target points.

When Location source is “Internal SOP” or “External SOP”, get the points from this named group in the SOP geometry.

When Location source is “First input’s primitives”, this is the scene graph paths of the primitives whose positions you want to use as target points. When Location source is “First input’s points”, this is a the scene graph path(s) of one or more geometry prims containing target points (such as a polygonal mesh). In either case you can use pattern syntax to select multiple primitives.

You can delete or hide a certain percentage of the target points. This may be useful if the target points come from an overly dense point cloud, or to speed up display when you're first setting up the instancer. The default is “None” to not delete or hide any points.

When Prune mode is “Delete” or “Set visibility”, the percentage of points to delete or hide. This can be used to improve performance while setting up the operator.

Rotate the instanced primitives based on standard instancing SOP attributes on the points. These SOP attributes include N, up , and orient.

Scale the instanced primitives based on standard instancing SOP attributes on the points. These SOP attributes include scale and pscale.

Set the visibility of the Location primitives to “hidden” in the output. The default is on.

A list of attributes on the template points to copy to instances. When creating a Point Instancer, an array primvar will be created for each listed attribute, with an entry for each point’s value. When creating reference primitives, an attribute of the same name and type will be created on each primitive.

A prefix string for the names of prims created by this node. The node appends the point index to this string to create each name. This name is then appended to the Primitive path value to create the reference prim path. This is ignored if Use path attribute is on (below) and the path attribute exists.

Use a string attribute on the target points to create the reference prim path.

When Use path attribute is on, if a path attribute is not unique append an identifier to ensure uniqueness.

When Use path attribute is on, the name of a string attribute on each point containing the path to use for the prim created at that point. The path in this attribute is appended to the Primitive path value. If this attribute doesn’t exist, the node falls back to using Instance base name.

If the paths in the attribute aren’t unique, and Make primitive paths unique is off, the node will only create one reference per path. In this case the node will show a warning.

Whether the prim(s) you want to reference/instance onto the points is/are in the first input or the second input.

If Prototype source is “First input”, this parameter controls the composition type to use when creating references to the source primitives from within the “Prototypes” folder in the scene graph. This parameter can be “Reference”, “Inherit”, or “Specialize”. See inherits and specializes for more information about how these choices differ from a simple reference.

If Prototype source is “First input” and this is on, the node sets the visibility of the prims used as primitives to “hidden” in the output. The default is on.

If Prototype source is “Second input” and this is on, the node copies everything from the second input’s scene graph tree under a new prim and uses that as the prototype. This lets you build a node chain that builds the prototype and connect it to the second input, and not have to specify which prim in the second input to use.

If Prototype source is “Second input” and Use Entire Stage as Prototype is off, this controls whether to only copy the prototype primitives specified by Prototype Primitives, or the entire stage. The default is on.

Using this option can result in a smaller stage, but requires that the prototype sources are fully self-contained (for example they cannot refer to materials that sit elsewhere in the prim hierarchy).

This option allows the Prototype Primitives pattern to consist of a hard coded list of paths, where prims may not exist at all of the specified source locations. This works with prototype primitives coming from either the first or second input. Rather than generate an error or warning about missing prototype primitives, the node will do one of two things. If the destination prototype primitive already exists in the scene graph, this node does nothing to this existing primitive. The existing primitive at the prototype location is used as one of the instancer prototypes. If there is no primitive at the destination prototype location, then this node will create an empty typeless primitive at the required destination prototype location.

This mode is useful when adding prototypes to an existing point instancer.

When Use entire stage is on, this sets the kind of the prim the node creates as a parent for root prims from the second input. The default is None.

The scene graph path(s) of the primitive(s) you want to use as prototype(s). You can use pattern syntax to select multiple primitives.

When Prototype index is “Random”, the seed for the random number generator.

When Prototype index is “Index”, the index of the prototype to use, from the list of primitives in Prototype primitives. You can use an expression to choose the index based on some other factor.

An integer attribute on the target points that specifies the prototype to use.

A string attribute on the target points that specifies the name of the prototype to use.

A string attribute on the target points that specifies the path of the prototype to use.

When Prototype Index is “Index Attribute”, “Name Attribute” or “Path Attribute”, this toggle controls whether or not to emit a warning when an instance is skipped due to there being no match between the attribute data and the prototype list.