How to use Vector Math node in Oraphim

Type ID: motion.vector.math
Category: Vector

What this node does

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

The current Oraphim runtime registers 7 sockets and 12 properties for this node. Its main registered inputs are A, B, Scale; its main outputs are Vector, Scalar, Valid. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
A	in_a	Vector3
B	in_b	Vector3
Scale	in_scale	Float
Factor	in_factor	Float

Outputs

Socket	Key	Type
Vector	out_vector	Vector3
Scalar	out_scalar	Float
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Operation	operation	String	Math	Add
A X	aX	Float	Default A	0.0
A Y	aY	Float	Default A	0.0
A Z	aZ	Float	Default A	0.0
B X	bX	Float	Default B	0.0
B Y	bY	Float	Default B	1.0
B Z	bZ	Float	Default B	0.0
Scale	scale	Float	Parameters	1.0
Factor	factor	Float	Parameters	0.5
Refraction Ratio	eta	Float	Parameters	1.0
Minimum Length	minLength	Float	Length	0.0
Maximum Length	maxLength	Float	Length	1.0

How to use it

1. Add Vector Math from node search. Use motion.vector.math when you need the exact registry entry.
2. Connect a compatible Vector3 source to A. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Operation, A X, A Y first so you can see the node's effect in isolation.
4. Route Vector (Vector3) 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 Vector Math. Feed a compatible source into A. Change Operation away from its registry default and compare the result. Connect Vector 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

• Combine Vector — motion.vector.combine
• Separate Vector — motion.vector.separate
• Path Follow — motion.path.follow
• Sample Path — motion.path.sample
• Morph Paths — motion.shape.morph

Return to the complete Oraphim node reference.