How to use Separate Vector node in Oraphim

Type ID: motion.vector.separate
Category: Vector

What this node does

The Separate 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 6 sockets and 3 properties for this node. Its main registered inputs are Vector; its main outputs are X, Y, Z. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Vector	in_vector	Vector3

Outputs

Socket	Key	Type
X	out_x	Float
Y	out_y	Float
Z	out_z	Float
Length	out_length	Float
Normalized	out_normalized	Vector3

Controls

Control	Key	Type	Group	Registry default
Default X	x	Float	Default	0.0
Default Y	y	Float	Default	0.0
Default Z	z	Float	Default	0.0

How to use it

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

• Combine Vector — motion.vector.combine
• Vector Math — motion.vector.math
• Path Follow — motion.path.follow
• Sample Path — motion.path.sample
• Morph Paths — motion.shape.morph

Return to the complete Oraphim node reference.