How to use Quaternion Math node in Oraphim

Type ID: motion.rotation.quaternion
Category: Transform

What this node does

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

The current Oraphim runtime registers 9 sockets and 11 properties for this node. Its main registered inputs are A Quaternion, B Quaternion, Euler Degrees; its main outputs are Quaternion, Euler Degrees, Vector. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
A Quaternion	in_a	Vector4
B Quaternion	in_b	Vector4
Euler Degrees	in_euler	Vector3
Vector	in_vector	Vector3
Factor	in_factor	Float

Outputs

Socket	Key	Type
Quaternion	out_quaternion	Vector4
Euler Degrees	out_euler	Vector3
Vector	out_vector	Vector3
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Operation	operation	String	Rotation	From Euler
A Euler X	aX	Float	Default A	0.0
A Euler Y	aY	Float	Default A	0.0
A Euler Z	aZ	Float	Default A	0.0
B Euler X	bX	Float	Default B	0.0
B Euler Y	bY	Float	Default B	0.0
B Euler Z	bZ	Float	Default B	0.0
Euler X	eulerX	Float	Euler	0.0
Euler Y	eulerY	Float	Euler	0.0
Euler Z	eulerZ	Float	Euler	0.0
Factor	factor	Float	Blend	0.5

How to use it

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

• Look At Transform — motion.transform.look_at
• Orient Constraint — motion.constraint.orient
• Compose Matrix — motion.matrix.compose
• Decompose Matrix — motion.matrix.decompose
• Distance Constraint — motion.constraint.distance

Return to the complete Oraphim node reference.