How to use Parent Constraint node in Oraphim

Type ID: motion.constraint.parent
Category: Transform

What this node does

The Parent 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 4 properties for this node. Its main registered inputs are Local Transform, Parent Transform, Offset Transform; its main outputs are World Transform, Position, Valid. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Local Transform	in_local	Matrix
Parent Transform	in_parent	Matrix
Offset Transform	in_offset	Matrix
Weight	in_weight	Float

Outputs

Socket	Key	Type
World Transform	out_matrix	Matrix
Position	out_position	Vector3
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Weight	weight	Float	Constraint	1.0
Inherit Translation	inheritTranslation	Bool	Channels	1.0
Inherit Rotation	inheritRotation	Bool	Channels	1.0
Inherit Scale	inheritScale	Bool	Channels	1.0

How to use it

1. Add Parent Constraint from node search. Use motion.constraint.parent when you need the exact registry entry.
2. Connect a compatible Matrix source to Local Transform. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Weight, Inherit Translation, Inherit Rotation first so you can see the node's effect in isolation.
4. Route World Transform (Matrix) 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 Parent Constraint. Feed a compatible source into Local Transform. Change Weight away from its registry default and compare the result. Connect World Transform 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
• 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.