How to use Compose Matrix node in Oraphim

Type ID: motion.matrix.compose
Category: Transform

What this node does

The Compose Matrix 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 7 sockets and 10 properties for this node. Its main registered inputs are Translation, Rotation, Scale; its main outputs are Matrix, Inverse, Determinant. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Translation	in_translation	Vector3
Rotation	in_rotation	Vector3
Scale	in_scale	Vector3

Outputs

Socket	Key	Type
Matrix	out_matrix	Matrix
Inverse	out_inverse	Matrix
Determinant	out_determinant	Float
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Translation X	tx	Float	Translation	0.0
Translation Y	ty	Float	Translation	0.0
Translation Z	tz	Float	Translation	0.0
Rotation X	rx	Float	Rotation	0.0
Rotation Y	ry	Float	Rotation	0.0
Rotation Z	rz	Float	Rotation	0.0
Scale X	sx	Float	Scale	1.0
Scale Y	sy	Float	Scale	1.0
Scale Z	sz	Float	Scale	1.0
Rotation Order	rotationOrder	String	Rotation	XYZ

How to use it

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

• Matrix Math — motion.matrix.math
• Decompose Matrix — motion.matrix.decompose
• Look At Transform — motion.transform.look_at
• Orient Constraint — motion.constraint.orient
• Parent Constraint — motion.constraint.parent

Return to the complete Oraphim node reference.