How to use Limit Transform node in Oraphim

Type ID: motion.constraint.limit_transform
Category: Transform

What this node does

The Limit Transform 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 21 properties for this node. Its main registered inputs are Transform; its main outputs are Transform, Translation, Euler Rotation. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Transform	in_matrix	Matrix

Outputs

Socket	Key	Type
Transform	out_matrix	Matrix
Translation	out_translation	Vector3
Euler Rotation	out_rotation	Vector3
Scale	out_scale	Vector3
Was Limited	out_limited	Bool
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Limit Translation	limitTranslation	Bool	Translation	1.0
Minimum X	minTX	Float	Translation	-1000000.0
Maximum X	maxTX	Float	Translation	1000000.0
Minimum Y	minTY	Float	Translation	-1000000.0
Maximum Y	maxTY	Float	Translation	1000000.0
Minimum Z	minTZ	Float	Translation	-1000000.0
Maximum Z	maxTZ	Float	Translation	1000000.0
Limit Rotation	limitRotation	Bool	Rotation	0.0
Minimum X	minRX	Float	Rotation	-180.0
Maximum X	maxRX	Float	Rotation	180.0
Minimum Y	minRY	Float	Rotation	-180.0
Maximum Y	maxRY	Float	Rotation	180.0
Minimum Z	minRZ	Float	Rotation	-180.0
Maximum Z	maxRZ	Float	Rotation	180.0
Limit Scale	limitScale	Bool	Scale	0.0
Minimum X	minSX	Float	Scale	0.0
Maximum X	maxSX	Float	Scale	1000000.0
Minimum Y	minSY	Float	Scale	0.0
Maximum Y	maxSY	Float	Scale	1000000.0
Minimum Z	minSZ	Float	Scale	0.0
Maximum Z	maxSZ	Float	Scale	1000000.0

How to use it

1. Add Limit Transform from node search. Use motion.constraint.limit_transform when you need the exact registry entry.
2. Connect a compatible Matrix source to Transform. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Limit Translation, Minimum X, Maximum X first so you can see the node's effect in isolation.
4. Route 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 Limit Transform. Feed a compatible source into Transform. Change Limit Translation away from its registry default and compare the result. Connect 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
• Parent Constraint — motion.constraint.parent
• Distance Constraint — motion.constraint.distance
• Point Constraint — motion.constraint.point
• Scale Constraint — motion.constraint.scale

Return to the complete Oraphim node reference.