How to use Orient Constraint node in Oraphim

Type ID: motion.constraint.orient
Category: Transform

What this node does

The Orient 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 10 properties for this node. Its main registered inputs are Source, Target, Offset Euler; its main outputs are Quaternion, Euler, Matrix. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Source	in_source	Vector4
Target	in_target	Vector4
Offset Euler	in_offset	Vector3
Weight	in_weight	Float

Outputs

Socket	Key	Type
Quaternion	out_quaternion	Vector4
Euler	out_euler	Vector3
Matrix	out_matrix	Matrix
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Weight	weight	Float	Constraint	1.0
Source X	sx	Float	Source	0.0
Source Y	sy	Float	Source	0.0
Source Z	sz	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 Orient Constraint from node search. Use motion.constraint.orient when you need the exact registry entry.
2. Connect a compatible Vector4 source to Source. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Weight, Source X, Source Y first so you can see the node's effect in isolation.
4. Route Quaternion (Vector4) 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 Orient Constraint. Feed a compatible source into Source. Change Weight away from its registry default and compare the result. Connect Quaternion 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

• Parent Constraint — motion.constraint.parent
• Distance Constraint — motion.constraint.distance
• Limit Transform — motion.constraint.limit_transform
• Point Constraint — motion.constraint.point
• Scale Constraint — motion.constraint.scale

Return to the complete Oraphim node reference.