How to use Transform node in Oraphim

Type ID: fusion.transform
Category: Transform

What this node does

The 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 0 sockets and 29 properties for this node. Its main registered inputs are no fixed inputs; its main outputs are no fixed outputs. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

This node has no fixed input sockets in the current runtime registry.

Outputs

This node has no fixed output sockets in the current runtime registry.

Controls

Control	Key	Type	Group	Registry default
Position X	posX	Float	Transform	0.0
Position Y	posY	Float	Transform	0.0
Position Z	posZ	Float	3D / Anchor	0.0
Scale X	scaleX	Float	Transform	100.0
Scale Y	scaleY	Float	Transform	100.0
Scale Z	scaleZ	Float	3D / Anchor	100.0
Rotation Z	rotation	Float	Transform	0.0
Rotation X	rotX	Float	3D / Anchor	0.0
Rotation Y	rotY	Float	3D / Anchor	0.0
Anchor X	anchorX	Float	3D / Anchor	0.0
Anchor Y	anchorY	Float	3D / Anchor	0.0
Anchor Z	anchorZ	Float	3D / Anchor	0.0
Crop Left	cropLeft	Float	Cropping	0.0
Crop Right	cropRight	Float	Cropping	0.0
Crop Top	cropTop	Float	Cropping	0.0
Crop Bottom	cropBottom	Float	Cropping	0.0
Softness	cropSoftness	Float	Cropping	0.0
Opacity	opacity	Float	Composite	100.0
Time Remap	timeRemap	Float	Time	0.0
Path Controller	isPathController	Bool	Path	0.0
Path	splineAssetId	String	Path	0.0
Follow Path	pathFollowEnabled	Bool	Path	0.0
Position	pathOffset	Float	Path	0.0
Speed	pathSpeed	Float	Path	0.0
Rotation Offset	pathRotation	Float	Path	0.0
Banking	pathBanking	Float	Path	0.0
Loop	pathLoop	Bool	Path	0.0
Reverse	pathReverse	Bool	Path	0.0
Orient To Path	pathOrientToPath	Bool	Path	1.0

How to use it

1. Add Transform from node search. Use fusion.transform when you need the exact registry entry.
2. Place the node as a source/context operation; it has no fixed input socket in the current registry.
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. Because there is no fixed output socket, validate the graph context or downstream resource that this node is intended to affect.
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 Transform. Change Position X away from its registry default and compare the result. 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

• Surface Match / Planar Blend — fusion.surfacematch
• 3D Camera Tracker — fusion.cameratracker
• Advanced Color Correction — fusion.advanced_color_correction
• Audio — fusion.audio
• Audio Generate — fusion.audio_generate

Return to the complete Oraphim node reference.