Utilization

Performance

Note that this SOP is non-compilable and its utilization may be computationally heavy, so an alternative may be to use the Copy To Points SOP, which is more performance-optimized and is compilable.

Stamping with Local Variable

Once attributes are assigned within the Copy SOP, the following HScript expression can be used by upstream nodes to retrieve the mapped local variable for stamping operations..

Inputs

Input 1: Primitives To Copy

These are the primitives intended to be instantiated via the Copy Stamp SOP. The variables and attributes defined within the Copy Stamp SOP can be referenced in this incoming stream to vary parameters on a per copy basis.

Input 2: Template To Copy

This is the template for point positions that also carry specified attributes to associate and define the copy instances for each of them once these points have been processed through the Copy Stamp SOP.

Parameters

Copy

Number of Copies

The value defined in this parameter is referenced by the local variable $NCY.

Stamp

Attribute Stamps

Attributes directly from the template points incoming through Input 2. In lieu of this, point attributes can also be mapped to local variables and input in the Variable parameter/s below.

Variable (Multiple Fields)

Local variables that are to be associated with the copy instances are specified here using the local variable notation ($localvariable). As noted above, incoming template point attributes can be input here only once they have been mapped for use as local variables, such as through one of the following methods:

• Attribute Create SOP
• Map Point Attribute to Local Variable with VEX

Attribute

Resources

Local Variables

Reference: https://www.sidefx.com/docs/houdini/nodes/sop/copy.html