How to use Sample Path node in Oraphim

Type ID: motion.path.sample
Category: Vector

What this node does

The Sample Path 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 22 sockets and 13 properties for this node. Its main registered inputs are Path, Value, Reference Up; its main outputs are Position, Tangent, Normal. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Path	in_path	Geometry3D
Value	in_value	Float
Reference Up	in_up	Vector3
Roll	in_roll	Float

Outputs

Socket	Key	Type
Position	out_position	Vector3
Tangent	out_tangent	Vector3
Normal	out_normal	Vector3
Binormal	out_binormal	Vector3
Frame	out_matrix	Matrix
Quaternion	out_quaternion	Vector4
Euler Degrees	out_euler	Vector3
Radius	out_radius	Float
Path Tilt	out_tilt	Float
Progress	out_progress	Float
Distance	out_distance	Float
Total Length	out_length	Float
Curvature	out_curvature	Float
Signed Curvature	out_signed_curvature	Float
Curve Index	out_curve_index	Int
Curve Count	out_curve_count	Int
Sample Count	out_sample_count	Int
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Parameter	parameterMode	String	Sampling	Normalized
Value	value	Float	Sampling	0.0
Outside Range	wrapMode	String	Sampling	Clamp
Reverse	reverse	Bool	Sampling	0.0
Curve Index (-1 Longest)	curveIndex	Int	Path	0.0
Samples Per Segment	resolution	Int	Path	16.0
Use Mesh Edges As Paths	includeMeshEdges	Bool	Path	1.0
Forward Axis	forwardAxis	String	Frame	Positive X
Additional Roll	roll	Float	Frame	0.0
Reference Up X	upX	Float	Frame	0.0
Reference Up Y	upY	Float	Frame	1.0
Reference Up Z	upZ	Float	Frame	0.0
Advanced Outputs	advancedOutputs	Bool	Output	0.0

How to use it

1. Add Sample Path from node search. Use motion.path.sample when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Path. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Parameter, Value, Outside Range first so you can see the node's effect in isolation.
4. Route Position (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 Sample Path. Feed a compatible source into Path. Change Parameter away from its registry default and compare the result. Connect Position 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
• Morph Paths — motion.shape.morph
• Combine Vector — motion.vector.combine
• Vector Math — motion.vector.math
• Separate Vector — motion.vector.separate

Return to the complete Oraphim node reference.