How to use Morph Paths node in Oraphim

Type ID: motion.shape.morph
Category: Vector

What this node does

The Morph Paths 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 13 sockets and 9 properties for this node. Its main registered inputs are Path A, Path B, Progress; its main outputs are Path, Geometry, Resolved Progress. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Path A	in_shape_a	Path
Path B	in_shape_b	Path
Progress	in_progress	Float

Outputs

Socket	Key	Type
Path	out_path	Path
Geometry	out_geometry	Geometry3D
Resolved Progress	out_progress	Float
Length A	out_length_a	Float
Length B	out_length_b	Float
Sample Count	out_sample_count	Int
Reversed B	out_reversed_b	Bool
Closed	out_closed	Bool
Diagnostic	out_diagnostic	String
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Progress	progress	Float	Morph	0.0
Clamp Progress	clampProgress	Bool	Morph	1.0
Output Samples	sampleCount	Int	Sampling	64.0
Source Resolution	resolution	Int	Sampling	16.0
Curve A Index (-1 Longest)	curveIndexA	Int	Sources	0.0
Curve B Index (-1 Longest)	curveIndexB	Int	Sources	0.0
Use Mesh Edges As Paths	includeMeshEdges	Bool	Sources	1.0
Direction Alignment	alignment	String	Correspondence	Auto Reverse
Output Closure	closure	String	Output	Auto

How to use it

1. Add Morph Paths from node search. Use motion.shape.morph when you need the exact registry entry.
2. Connect a compatible Path source to Path A. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Progress, Clamp Progress, Output Samples first so you can see the node's effect in isolation.
4. Route Path (Path) 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 Morph Paths. Feed a compatible source into Path A. Change Progress away from its registry default and compare the result. Connect Path 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

• Path Follow — motion.path.follow
• Sample Path — motion.path.sample
• Vector Math — motion.vector.math
• Combine Vector — motion.vector.combine
• Separate Vector — motion.vector.separate

Return to the complete Oraphim node reference.