Node reference

How to use Matrix Math node in Oraphim

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

Updated August 28, 2026

How to use Matrix Math node in Oraphim

Type ID: motion.matrix.math
Category: Transform

What this node does

The Matrix 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 7 sockets and 1 properties for this node. Its main registered inputs are A, B, Vector; its main outputs are Matrix, Vector, Scalar. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
A in_a Matrix
B in_b Matrix
Vector in_vector Vector3

Outputs

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

Controls

Control Key Type Group Registry default
Operation operation String Matrix Multiply

How to use it

  1. Add Matrix Math from node search. Use motion.matrix.math when you need the exact registry entry.
  2. Connect a compatible Matrix source to A. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Operation 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 Matrix Math. Feed a compatible source into A. Change Operation 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.

Return to the complete Oraphim node reference.