How to use Distance Constraint node in Oraphim

Type ID: motion.constraint.distance
Category: Transform

What this node does

The Distance Constraint 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 7 sockets and 10 properties for this node. Its main registered inputs are Position, Target; its main outputs are Constrained Position, Direction, Distance. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Position	in_position	Vector3
Target	in_target	Vector3

Outputs

Socket	Key	Type
Constrained Position	out_position	Vector3
Direction	out_direction	Vector3
Distance	out_distance	Float
Correction	out_correction	Float
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Mode	mode	String	Constraint	Clamp Range
Minimum Distance	minimum	Float	Constraint	0.0
Maximum Distance	maximum	Float	Constraint	1000000.0
Exact Distance	distance	Float	Constraint	1.0
Position X	px	Float	Position	0.0
Position Y	py	Float	Position	0.0
Position Z	pz	Float	Position	0.0
Target X	tx	Float	Target	0.0
Target Y	ty	Float	Target	0.0
Target Z	tz	Float	Target	0.0

How to use it

1. Add Distance Constraint from node search. Use motion.constraint.distance when you need the exact registry entry.
2. Connect a compatible Vector3 source to Position. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Mode, Minimum Distance, Maximum Distance first so you can see the node's effect in isolation.
4. Route Constrained 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 Distance Constraint. Feed a compatible source into Position. Change Mode away from its registry default and compare the result. Connect Constrained 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

• Orient Constraint — motion.constraint.orient
• Parent Constraint — motion.constraint.parent
• Point Constraint — motion.constraint.point
• Scale Constraint — motion.constraint.scale
• Limit Transform — motion.constraint.limit_transform

Return to the complete Oraphim node reference.