Node reference

How to use Decompose Matrix node in Oraphim

Use the Decompose Matrix node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID motion.matrix.decompose.

Updated August 28, 2026

How to use Decompose Matrix node in Oraphim

Type ID: motion.matrix.decompose
Category: Transform

What this node does

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

Inputs

Socket Key Type
Matrix in_matrix Matrix

Outputs

Socket Key Type
Translation out_translation Vector3
Euler Rotation out_rotation Vector3
Scale out_scale Vector3
Quaternion out_quaternion Vector4
Valid out_valid Bool

Controls

This node has no registered editable properties; use its sockets and graph context.

How to use it

  1. Add Decompose Matrix from node search. Use motion.matrix.decompose when you need the exact registry entry.
  2. Connect a compatible Matrix source to Matrix. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust socket/context behavior first so you can see the node's effect in isolation.
  4. Route Translation (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 Decompose Matrix. Feed a compatible source into Matrix. Connect Translation 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.

Return to the complete Oraphim node reference.