On this page | |
Since | 19.5 |
Overview ¶
This node is very similar to the Edit Properties LOP. But instead of adding spare parameters to this node, you must direct it to another node from which it reads parameters that correspond to attributes on prims in the scene graph tree. When you edit these parameters on the other node, this node authors equivalent changes to the equivalent USD attributes.
This node is particularly useful inside a locked HDA, but where the set of USD attributes to be controlled is not known when the HDA is created. In this case, an Edit Properties LOP cannot be used because the node is locked. Instead, with a node of this type, spare parameters can be added to the editable HDA parent node to drive the USD attributes.
Control pop-up menus ¶
Tips ¶
-
On an Edit Properties LOP, the
@numprim
,@prim
, and@primpath
local variables can be used to produce a different attribute value for each primitive modified by the node. Since local variables can only be used on the node that defines them, the referenced node cannot use these variables. Instead, this node has default parameters, each of which is set to evaluate one of these local variables. The referenced node can then use a ch() expression to evaluate the local variable owned by this node to generate per-primitive values. -
A node of this type can also optionally have parameters (on this node itself, not the referenced node) that validate the node’s parameters and trigger warnings or errors if requirements are not met. To use this feature, two parameters are used:
errorseverity
An ordered menu indicating whether the validation message should be presented as a Message, Warning, or Error (using the values
0
,1
, and2
respectively).errormsg
The message to be presented to the user. If this parameter returns an empty string, no message is added to the node.
This node belongs to a class of nodes that create or edit USD prims directly. These nodes operate in Create mode or Edit mode. This is controlled by a Create primitives checkbox or a Create/Edit popup menu. In create mode, the node creates new prims. In edit mode, the node changes the attributes on an existing prim. The Edit mode has two variations. Edit will not modify primitives which have a houdini:editable
attribute set to false
. Force edit will modify a primitive regardless of the existence or value of this attribute. This attribute can be set on a primitive using the Configure Primitives LOP.
Parameters that correspond to a USD attribute have a pop-up menu to the left that controls how the node authors the attribute.
In addition to that, any connectable USD attributes (i.e., the ones in the inputs:
namespace) will have menu items that allow disconnecting them from their sources.
Pop-up menu item |
Meaning |
---|---|
Set or Create |
Sets the attribute to the given value, whether it previously existed or not. |
Set If Exists |
Only set the attribute to the given value if it previously existed. Use this mode to make sure an attribute is only set on primitives of the correct type. For example, only |
Block |
Makes the attribute appear to not exist, so it takes on its default value. (If the attribute doesn’t already exist on the prim, this does nothing.) |
Disconnect Input |
Deletes the attribute input connection to its source. Input connections take precedence over attribute values, so disconnecting an input allows the attribute value to take effect. |
Do Nothing |
Ignore this parameter, don’t create or change the attribute in any way. |
Parameters ¶
Sampling Behavior
Cooking this node can generate many USD time samples, rather than just a single time sample at the current time. This can be equivalent to having a Cache LOP following this node, but it will evaluate much faster, and does not cache data from any other nodes. This allows animated data to be authored to USD without introducing a node time dependency which would then cause all following nodes to also be time dependent. This can vastly improve playback performance of some LOP Networks.
In all sampling modes, if a parameter on this node does not vary with time, and does not rely on other time sampled data from the stage, only a single default value will be generated in USD for the corresponding attribute. USD time samples are only generated for parameters that may vary over time.
Sample Current Frame
A single time sample will be generated for the current time.
Sample Frame Range If Input Is Not Time Dependent
If the input to this node is time dependent, this node behaves as if it is in Sample current frame
mode. Otherwise it behaves as if it is in Sample frame range
mode.
Sample Frame Range
The Start/End/Inc parameter is used to generate multiple times at which this node’s parameters are evaluated, and a USD time sample is created for each attribute at each one of these times.
Start/End/Inc
When the Sampling behavior is Sample frame range
, this parameter controls the number and spacing of base time samples to be generated by this node. The default values of this parameter are @fstart
, @fend
, and @finc
. These values correspond to the start, end, and step size of the global Houdini animation settings when interacting with Houdini. When using a ROP node to generate a range of frames, these values correspond to the start, end, and increment values specified on the ROP node being executed. This default ensures that a USD file written to disk will contain time samples for exactly the frame range requested by the ROP (regardless of the Houdini animation settings).
Subframe Sampling
For each primary sample generated by this node, these parameters can cause additional samples to be generated around that primary sample time. This is most often used to ensure that accurate data exists at exactly the camera shutter open and close times, as well as at the primary sample time.
Shutter
Controls the method used to specify the shutter open and close times relative to the primary sample times.
Specify Manually
The Shutter Open/Close parameter values provide exact offset values relative to the primary sample time.
Use Camera Prim
The Camera Prim parameter provides the scene graph path of a camera primitive from which the shutter open and close times are extracted to provide the offset values relative to the primary time sample.
Shutter Open/Close
When Shutter is set to Specify Manually, these two offset values are added to the primary sample time to indicate the shutter open and close times. The open time should be less than or equal to zero, and the close time should be greater than or equal to zero.
Camera Prim
When Shutter is set to Use Camera Prim, this is the scene graph path of a camera prim on the input node’s stage. The shutter open and close attribute values are read from this primitive.
Samples
The number of subframe samples to create for each primary sample. These samples are evenly distributed between the shutter open and close times. Note that such an even distribution may or may not create a sample at exactly the primary sample time.
Always Include Frame Sample
When turned on, forces a sample to be created at exactly the primary sample time. If the Samples value, together with the shutter open and close times, already place a sample at the primary sample time, turning on this option has no effect. Otherwise, this option causes an addition sample to be added. This means that the actual number of samples per primary sample may in fact be one more than the number specified in the Samples parameter.
Action
Whether this node should create new prims, or edit existing prims. In addition, the Force Edit
option can be chosen to cause this node to ignore the houdini:editable
attribute on prims, and always edit the specified attributes. This is in contrast to the Edit
mode which will trigger a warning and not set attributes on prims with the houdini:editable
attribute set to false
.
Primitive Path
In create mode, this lets you control where in the scene graph to create the prim(s).
The default is usually /$OS
. This creates a primitive at the root level with the same name as the node (for example, /tube1
). This is a useful default for preventing naming conflicts, but terrible for organization. You should try to remember to change the Primitive path to a better value when you create prims.
For example, instead of naming models after the node that created them, you might want to name them after the geometry inside, and organize them under a /Models
branch.
The “Create primitives” section contains basic controls for how to create the new prim(s).
Primitives
In edit mode, the node has a Primitive pattern parameter. This lets you specify the prim(s) the node should operate on. You can click the select button beside the text box to select the primitives from the scene graph tree. You can also use primitive patterns for advanced matching, including matching all prims in a collection.
Initialize Parameters
Changes the state of all control menu parameters to Do Nothing
, so that this node will not apply any changes. Also grabs the current values of each property from the first Primitives match, and sets the values of the corresponding parameters to match. This means that changing any parameter’s control menu to Set or Create
mode will set the property to its current value, making it easier to apply changes to an existing value rather than setting a brand new value.
Create Primitives
This section only appears when the node is creating primitives.
For example:
-
If you want to create a new cube primitive at
/world/objects/cube1
on an empty stage: Set Primitive Specifier to “Define”, and the Parent Primitive Type to “Xform”. -
If you want to override the radius of a sphere at
/world/objects/sphere1
: Set Primitive Specifier to “Over”, and the Parent Primitive Type to None. This makes sure the primitive types of any existing ancestor prims are not be modified by this node.
Primitive Count
The number of primitives to create.
Primitive Kind
Set all created prims to have this kind.
Primitive Specifier
The USD operator to use when creating the new prims.
Define
Authors a completely new prim. Use this if you want to create a brand new prim or replace an existing prim.
Over
Authors an override of an existing prim. Attributes not explicitly authored on this prim will get their values from the existing prim on the lower layer.
Class
Define a primitive class. This is usually not necessary unless you are doing deep USD magic.
Class Ancestor
If the Specifier is Define
or Over
, this parameter will cause some ancestor primitives to be authored with a specifier of Class
. This makes it easy to create an Over
or Define
within a Class
without having to use two separate nodes. When the Specifier is Class
, this parameter is disabled because the entire primitive hierarchy is already authored as Class
primitives.
Parent Primitive Type
If any parents of a path in Primitive paths do not exist, this node will automatically create them. In this case, it will create parent nodes of this type.
Parameters From Node
Path to the node holding the parameters that are evalauted to set USD attributes on the specified primitives.
Parameters
A string pattern that is matched against the parameters on the referenced node to determine which parameters will be used to author USD attributes. Parameters that use “encoded” names to correspond to namespaced attributes will match either the encoded or the decoded for of the parameter name. Control menu parameters will also be automatically included if the corresponding attribute parameter matches the pattern.
Prim Local
This parameter contains the @prim
local variable so it can be referenced by the source node’s parameters.
Prim Path Local
This parameter contains the @primpath
local variable so it can be referenced by the source node’s parameters.
Prim Count Local
This parameter contains the @numprim
local variable so it can be referenced by the source node’s parameters.