|On this page|
It can be used send a command or custom code to the server, depending on what the server accepts. The Houdini server runs Python code that uses the HOM API, the Maya server uses MEL or Python and the generic command server uses the format defined by its server implementation.
When used with a Maya server, the script text is assumed to be python code unless
//mel is the first line of the script, in which case the script text is treated as MEL code.
The path to the file containing a serialization representation of the Command Script.
The name of the shared server instance the work item will attempt to use when running its command script.
Work Item Generation
Whether this node generates static or dynamic work items. You should generally leave this set to "Automatic" unless you know the node’s work items can be computed statically, or that they need to be generated dynamically.
This node always creates dynamic work items: it waits until the upstream work items are known, and generates new work items from the upstream work items.
This node always creates static work items: it creates the number of work items it thinks it needs based on the parameters (and any upstream static items) before the network runs.
If the input is static (a static processor, or a partitioner with only static inputs, or a mapper), this node generates static work items, otherwise it generates dynamic work items.
Result Data Tag
If the command produces results, the data will be tagged with string.
The code to send to the shared server. If the server is a Houdini Server this should be Python code, and can make use of the HOM API. If the server is a Maya Server this parm should contain MEL code.
The following examples include this node.
This example demonstrates how to create generic command chains.