Node reference

How to use Combine Vector node in Oraphim

Use the Combine Vector node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID motion.vector.combine.

Updated August 28, 2026

How to use Combine Vector node in Oraphim

Type ID: motion.vector.combine
Category: Vector

What this node does

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

The current Oraphim runtime registers 7 sockets and 4 properties for this node. Its main registered inputs are X, Y, Z; its main outputs are Vector, Vector 4, Length. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
X in_x Float
Y in_y Float
Z in_z Float
W in_w Float

Outputs

Socket Key Type
Vector out_vector Vector3
Vector 4 out_vector4 Vector4
Length out_length Float

Controls

Control Key Type Group Registry default
X x Float Components 0.0
Y y Float Components 0.0
Z z Float Components 0.0
W w Float Components 1.0

How to use it

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