How to use Motion Constraint node in Oraphim

Type ID: geometry.motion_constraint
Category: Transform

What this node does

The Motion 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 13 sockets and 11 properties for this node. Its main registered inputs are Geometry, Mode, Target X; its main outputs are Geometry. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Geometry	geometry	Geometry3D
Mode	mode	String
Target X	targetX	Float
Target Y	targetY	Float
Target Z	targetZ	Float
Strength	strength	Float
Min X	minX	Float
Min Y	minY	Float
Min Z	minZ	Float
Max X	maxX	Float
Max Y	maxY	Float
Max Z	maxZ	Float

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Mode	mode	String	Inputs	Follow Target
Target X	targetX	Float	Inputs	0.0
Target Y	targetY	Float	Inputs	0.0
Target Z	targetZ	Float	Inputs	0.0
Strength	strength	Float	Inputs	1.0
Min X	minX	Float	Inputs	-100000.0
Min Y	minY	Float	Inputs	-100000.0
Min Z	minZ	Float	Inputs	-100000.0
Max X	maxX	Float	Inputs	100000.0
Max Y	maxY	Float	Inputs	100000.0
Max Z	maxZ	Float	Inputs	100000.0

How to use it

1. Add Motion Constraint from node search. Use geometry.motion_constraint when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Geometry. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Mode, Target X, Target Y first so you can see the node's effect in isolation.
4. Route Geometry (Geometry3D) 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 Motion Constraint. Feed a compatible source into Geometry. Change Mode away from its registry default and compare the result. Connect Geometry 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

• Clone Elements — geometry.clone_elements
• Fillet Curve — geometry.curve_fillet
• Layout Elements — geometry.layout_elements
• Mesh to Volume — geometry.mesh_to_volume
• Motion FX — geometry.motion_fx

Return to the complete Oraphim node reference.