| On this page |
This page lists the metadata that are available on graph nodes and ports.
Tags ¶
Properties ¶
Properties are special metadata that are stored on graphs as detail attributes or on graph nodes as point attributes. Properties are stored in a dictionary attribute called properties, and can contain information like rig parameter limits or the look of a control shape. The animate state picks up on these properties when assembling an animation scene.
Note
There are no port properties.
There are predefined entries in the properties dictionary, and they are listed in the sections below. In addition to the predefined entries, you can also add custom entries to the properties dictionary.
Point properties ¶
Point properties are stored on graph nodes. To view a graph node’s properties:
-
In the APEX network view,
click the graph node and select Properties.
or
-
In the geometry spreadsheet, select
Points on the top toolbar.
click the entry under the properties column and select Inspect.
The following are the predefined properties on graph nodes:
Property |
Type |
Description |
|---|---|---|
control |
|
A dictionary that contains information on the look of the control in the viewport. The format of the control dictionary is: control: {
color: Vector3
shapeoffset: Matrix4
shapeoverride: String
visibility: Int
}
For example: "control":{
"color":[0.5,0,1],
"shapeoffset":[0.3,0,0,0,0,0.3,0,0,0,0,0.3,0,0,0,0,1],
"shapeoverride":"torus",
"visibility":1
}
|
color |
|
The color of the control. |
shapeoffset |
|
The position of the control. |
shapeoverride |
|
The shape of the control. |
visibility |
|
The visibility of the control in the animate state. |
max, min |
|
A soft limit on the rig transform parameters. The Vector3 values are the limits on the x, y, and z values of the parameter. The user can control whether or not to enforce the limits or use the limits as a visual indicator in the animate state. See transform limits for more information. The format of the [max|min]:<parameter_name>: [<x_value>, <y_value>, <z_value>] For example: "max:t":[5, 5, 5] "min:t":[-5, -5, -5] |
max_lock, min_lock |
|
A hard limit on the rig transform parameters. The Vector3 values are the limits on the x, y, and z values of the parameter. This cannot be turned off in the animate state. See transform limits for more information. The format of the [max_lock|min_lock]:<parameter_name>: [<x_value>, <y_value>, <z_value>] For example: "max_lock:t":[10, 10, 10] "min_lock:t":[-10, -10, -10] |
mapping |
|
Specifies the mapping between rigs/skeletons to TransformObject nodes. This is useful for mapping skeleton joints to controls, or in the case where one rig drives another, mapping the controls between two rigs. This mapping information is stored on the The format of the mapping:<skeleton|rig>: <element_name|APEX_path_pattern> For example: "mapping:Base.skel":"C_pelvis" |
mapping_xform |
|
Transform data used to bind skeleton joints to their corresponding controls (TransformObject nodes). The format of the mapping_xform:<skeleton>: [<transform>] For example: "mapping_xform:Base.skel":[0.9,0.3,0.1,0,...] |
The mapping and mapping_xform properties can be set using an APEX Map Character SOP, and the other properties can be set using an
APEX Configure Controls SOP.
Below is an example of a properties point dictionary attribute on a graph node:
{
"control":{
"color":[0.5,0,1],
"shapeoffset":[0.3,0,0,0,0,0.3,0,0,0,0,0.3,0,0,0,0,1],
"shapeoverride":"torus",
"visibility":1
},
"max:t":[5, 5, 5],
"min:t":[-5, -5, -5],
"max_lock:t":[10, 10, 10],
"min_lock:t":[-10, -10, -10],
"mapping:Base.skel":"lowerarm_l",
"mapping_xform:Base.skel":[0.9,0.3,0.1,0,...]
}Detail properties ¶
Detail properties are stored on the graph itself. To view a graph’s detail properties:
-
In the geometry spreadsheet, select
Detail on the top toolbar.
-
click the value of properties and select Inspect.
The following are the predefined properties on graphs:
Property |
Type |
Description |
|---|---|---|
mirror_axis |
|
The plane that the rig is mirrored across. The vector is the normal vector of the plane. For example, if the rig is mirrored across the YZ plane, this value is |
mirror_pattern |
|
A dictionary that defines how the rig control names are mirrored. The dictionary has two keys - "mirror_pattern":{
"left_pattern":"L_*",
"right_pattern":"R_*"
}
The default mirroring pattern is |
frame_input |
|
The input port on the graph that stores the value of the current frame. The input port must be a float value. For example, the property |
time_input |
|
The input port on the graph that stores the value of the current time. The input port must be a float value. For example, the property |
fps_input |
|
The input port on the graph that stores the current frames per second. The input port must be a float value. For example, the property |
sidefx::wire_style |
|
The wiring style for the graph. 0 is for straight lines and 1 is for rounded connections. |
Below is an example of a properties detail dictionary attribute on a graph:
{
"fps_input":"my_fps",
"frame_input":"my_frame",
"mirror_axis":[1,0,0],
"mirror_pattern":{
"left_pattern":"L_*",
"right_pattern":"R_*"
},
"sidefx::wire_style":1,
"time_input":"my_time"
}| To... | Do this |
|---|---|
|
To add and modify the |
Use an For point properties:
For detail properties: |
|
View the properties on a graph |
For point properties:
For detail properties:
|
Attributes ¶
APEX graph geometry have the following attributes:
Name |
Class |
Type |
Description |
|---|---|---|---|
|
point |
|
The name of the node. |
|
point |
|
The callback name (node type) of the node. |
|
point |
|
The color of the node. |
|
vertex |
|
The name of the port. |
|
vertex |
|
The subport name or renamed ports. |
|
vertex |
|
The index number of the port. |
|
point |
|
A dictionary of default values for the ports. |
point |
|
An array of strings that are used as identifiers for graph nodes. Tags can be matched using the APEX path pattern function |
|
point |
|
A dictionary of additional metadata on the node. Properties can be matched using the APEX path pattern function |
Callbacks ¶
There are special callback names for some of the graph elements:
Node |
Callback name |
|---|---|
Graph input node |
|
Graph output node |
|
Subnet |
|
Sticky note |
|