Node reference

How to use Convert Transform Space node in Oraphim

Use the Convert Transform Space node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID motion.transform.space_convert.

Updated August 28, 2026

How to use Convert Transform Space node in Oraphim

Type ID: motion.transform.space_convert
Category: Transform

What this node does

The Convert Transform Space 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 5 sockets and 1 properties for this node. Its main registered inputs are Transform, Parent Transform; its main outputs are Transform, Parent Inverse, Valid. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Transform in_matrix Matrix
Parent Transform in_parent Matrix

Outputs

Socket Key Type
Transform out_matrix Matrix
Parent Inverse out_parent_inverse Matrix
Valid out_valid Bool

Controls

Control Key Type Group Registry default
Conversion mode String Space Local To World

How to use it

  1. Add Convert Transform Space from node search. Use motion.transform.space_convert when you need the exact registry entry.
  2. Connect a compatible Matrix source to Transform. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Conversion first so you can see the node's effect in isolation.
  4. Route Transform (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 Convert Transform Space. Feed a compatible source into Transform. Change Conversion away from its registry default and compare the result. Connect Transform 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.