|On this page|
This node runs a compiled block defined elsewhere to process this node’s inputs, as if the referenced block was wired in instead of this node.
This is useful in two ways:
You can use it to duplicate a block of functionality in different places in the network without having to copy or reference nodes.
You can create a digital asset with a parameter that accepts a reference to a compiled block, and then use that block as part of the asset’s operation. For example, if you made an asset that generated a tree, you could allow the user to pass in an optional block to process each leaf as the asset generates it.
The parameters on the nodes in the invoked block will be evaluated in their original locations.
You can specify a number of inputs on this node. Each input can "override" the input of a Block Begin Compile node in the referenced block. (Remember that a compiled block must have a Begin Compile node at each "entry point" into the block.)
The inputs are matched to the Begin Compile nodes by the value of their Input name parameters.
For example, if you set the Input name parameter on a Block Begin Compile node in the block to
piece, and then create an input on this node and also set its Input name to
piece, it will override the input for that Begin Compile node when this node executes the block.
If the block has a Block Begin Compile node that is not overriden by an input to this node, it will execute using its own input where the block is defined.
For example, if the block has two Begin Compile nodes with Input name values of
bar, but this node only has one input that overrides
foo, when this node executes the block, the Begin Compile node with Input name
foowill have its input override this node’s input, but the Begin Compile node with Input name
barwill cook its actual input.
A path to the last node in the compiled block you want to execute.
Number of inputs
Controls the number of inputs this node has.
The value of the Input name on the Block Begin Compile node you want to override with this input. This is not a path to the Begin Compile node itself.
If you leave this blank, this input uses its connected geometry, if any. However, if you specify a path to a geometry node here, it will use that geometry as input instead.
Whether to unload the executed block’s intermediate data (or cache it on this node). Since compiled blocks are usually used for repeated sections that shouldn’t cache, this parameter defaults to always unload. This setting uses less memory.
Don’t unload (that is, cache the executed block’s intermediate data).
Use node’s flag
Check this node’s Unload flag for whether to unload the cache.
Always unload the intermediate data (this is, do not cache).