Ops and Proxies¶
Deferred Ops¶
The effect of certain nodes and operations can be deferred until render time.
This is done by adding an ops
attribute group to the target scene graph
location, specifying the operations to run. Nodes that support deferred
evaluation include OpScript and GenericOp. Deferred
operations are run by the OpResolve node/op, which is part of the
implicit resolver chain.
Type |
Attribute |
Description |
---|---|---|
|
|
A group specifying a single Op to run. The modifier name is user-chosen and has no special meaning. |
|
|
The type of Op to run. |
|
|
The arguments to the Op. Varies by Op type. |
|
|
Referred to as System Op Args, these arguments are used by some Ops. |
|
|
List of resolve IDs. These are arbitrary string tags that are matched
against the resolve IDs passed to OpResolve. Two resolve
IDs - |
|
|
If |
Deferred Material Ops¶
Ops can also be run at material resolve time. The attribute convention is the
same as above, except that ops are nested under a material.ops
group,
rather than ops
.
Viewer Proxy Ops¶
A similar convention can also be used to specify viewer proxies for scene graph locations.
Type |
Attribute |
Description |
---|---|---|
|
|
Sets the frame range for which the proxy is active. |
|
|
If set to |
|
|
A group specifying a single Op to use for a proxy. See above for further details. |