How to use Point Constraint node in Oraphim

Type ID: motion.constraint.point
Category: Transform

What this node does

The Point 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 8 sockets and 13 properties for this node. Its main registered inputs are Position, Target, Offset; its main outputs are Position, Correction, 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
Offset	in_offset	Vector3
Weight	in_weight	Float

Outputs

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

Controls

Control	Key	Type	Group	Registry default
Weight	weight	Float	Constraint	1.0
Affect X	affectX	Bool	Channels	1.0
Affect Y	affectY	Bool	Channels	1.0
Affect Z	affectZ	Bool	Channels	1.0
Position X	px	Float	Source	0.0
Position Y	py	Float	Source	0.0
Position Z	pz	Float	Source	0.0
Target X	tx	Float	Target	0.0
Target Y	ty	Float	Target	0.0
Target Z	tz	Float	Target	0.0
Offset X	ox	Float	Offset	0.0
Offset Y	oy	Float	Offset	0.0
Offset Z	oz	Float	Offset	0.0

How to use it

1. Add Point Constraint from node search. Use motion.constraint.point 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 Weight, Affect X, Affect Y 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 Point Constraint. Feed a compatible source into Position. Change Weight 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

• Distance Constraint — motion.constraint.distance
• Orient Constraint — motion.constraint.orient
• Parent Constraint — motion.constraint.parent
• Scale Constraint — motion.constraint.scale
• Limit Transform — motion.constraint.limit_transform

Return to the complete Oraphim node reference.