How to use Formula node in Oraphim

Type ID: motion.expression.formula
Category: Utility

What this node does

The Formula node is registered in Oraphim's Utility category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 8 sockets and 6 properties for this node. Its main registered inputs are X, Y, Z; its main outputs are Value, Valid, Error. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
X	in_x	Float
Y	in_y	Float
Z	in_z	Float
Time	in_time	Float
Frame	in_frame	Float

Outputs

Socket	Key	Type
Value	out_value	Float
Valid	out_valid	Bool
Error	out_error	String

Controls

Control	Key	Type	Group	Registry default
Expression	expression	String	Formula	sin(t * 6.28318530718)
X	x	Float	Defaults	0.0
Y	y	Float	Defaults	0.0
Z	z	Float	Defaults	0.0
Frames Per Second	fps	Float	Timeline	60.0
Fallback	fallback	Float	Error	0.0

How to use it

1. Add Formula from node search. Use motion.expression.formula when you need the exact registry entry.
2. Connect a compatible Float source to X. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Expression, X, Y first so you can see the node's effect in isolation.
4. Route Value (Float) into a compatible downstream node, viewer, or output path.
5. Preview a representative frame, change one input/control at a time, and save/reopen reusable graphs to verify persistence.

Practical example

Create a small test graph with Formula. Feed a compatible source into X. Change Expression away from its registry default and compare the result. Connect Value to a compatible downstream stage so the result is visible. Keeping this test graph small makes socket-type, context, and parameter mistakes easier to diagnose before the node is used in a production graph.

Troubleshooting

• If a connection is rejected, compare the exact socket data types in the tables above; Oraphim graph connections are typed.
• If the result looks unchanged, confirm this node is on the active path to the viewer/output and that the expected graph/resource is selected.
• If a control is unavailable, check required inputs and whether the property belongs to an internal or mode-dependent group.
• If a saved graph behaves differently later, reopen it and verify node identity, connections, and edited property values before rendering.

Related nodes

• Boolean Math — motion.logic.boolean
• Clamp — motion.value.clamp
• Compare — motion.logic.compare
• Curve Map — motion.value.curve
• Map Range — motion.value.map_range

Return to the complete Oraphim node reference.