How to use Look At Transform node in Oraphim

Type ID: motion.transform.look_at
Category: Transform

What this node does

The Look At 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 9 sockets and 11 properties for this node. Its main registered inputs are Position, Target, Up; its main outputs are Transform, Quaternion, Euler Degrees. 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
Up	in_up	Vector3

Outputs

Socket	Key	Type
Transform	out_matrix	Matrix
Quaternion	out_quaternion	Vector4
Euler Degrees	out_euler	Vector3
Direction	out_direction	Vector3
Distance	out_distance	Float
Valid	out_valid	Bool

Controls

Control	Key	Type	Group	Registry default
Position X	px	Float	Position	0.0
Position Y	py	Float	Position	0.0
Position Z	pz	Float	Position	0.0
Target X	tx	Float	Target	0.0
Target Y	ty	Float	Target	0.0
Target Z	tz	Float	Target	-1.0
Up X	upX	Float	Orientation	0.0
Up Y	upY	Float	Orientation	1.0
Up Z	upZ	Float	Orientation	0.0
Roll	roll	Float	Orientation	0.0
Forward Axis	forwardAxis	String	Orientation	Negative Z

How to use it

1. Add Look At Transform from node search. Use motion.transform.look_at 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 Position X, Position Y, Position Z 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 Look At Transform. Feed a compatible source into Position. Change Position X 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

• Blend Transforms — motion.transform.blend
• Convert Transform Space — motion.transform.space_convert
• Layer Transform Animator — motion.transform.layer
• Orient Constraint — motion.constraint.orient
• Compose Matrix — motion.matrix.compose

Return to the complete Oraphim node reference.