Repository navigation
Export Nodes SourceIOFlexRawExpressionNode
REDxEYE edited this page Nov 20, 2026
·
1 revision
Category: Flex rules · Node ID: SourceIOFlexRawExpressionNode

Outputs a hand-written DMX flex expression. Use it for formulas the other expression nodes do not cover; it is the escape hatch for advanced Source Tools expressions.
None. The expression names controllers as plain text; it does not link to controller nodes.
| Socket | Type | Description |
|---|---|---|
| Value | Flex expression | The expression text (surrounding whitespace removed). Link to a rule's Value, or into other expression nodes. An empty expression fails the export. |
| Control | Meaning |
|---|---|
| DMX expression | The expression, e.g. smile * (1.0 - blink) ("Advanced Source Tools expression"). |
Expressions are checked when the model is built (parsed as an arithmetic expression), and only these parts are allowed:
-
Controller names as identifiers (letters, digits,
_, not starting with a digit). Each must exist in the rule set, i.e. be a controller linked to the Flex rules collector's Controllers input (after the name sanitizing shown on the controller node). Stereo controllers are referenced by their plain name; the export splits them intoleft_/right_where needed. -
Numbers such as
0.5or2. - The operators
+,-,*,/, unary-/+, and parentheses. - The functions
min(a, b)andmax(a, b); no other function.
Anything else (powers, comparisons, conditionals, other functions, unknown names) is rejected with an error naming the rule.
Type min(smile, 1.0 - blink) in DMX expression, link Value to a Shape flex rule Value, and make sure controllers smile and blink are linked to the collector.
- Unlike the other expression nodes it is not validated on the node; mistakes appear only at export or when the Blender driver preview is rebuilt.
- Controller names inside the text are not renamed if you rename the controller node.
- The Blender driver preview replaces each known controller name with a driver variable and copies the rest unchanged, so it only supports what Blender's driver expression language accepts (the allowed syntax above is within it). An expression that exceeds 255 bytes after variable substitution cannot be previewed, although it can still export.
- A Shape rule whose Value is a raw expression that merely equals a controller name is treated like a direct link for controller shapes and shape-key range purposes (it compares the exported text).
Back to Export Nodes