How to use Set Instance Transform node in Oraphim

Type ID: geometry.set_instance_transform
Category: Transform

What this node does

Changes instance transform on incoming geometry and passes the edited result downstream.

The current Oraphim runtime registers 4 sockets and 10 properties for this node. Its main registered inputs are Instances, Selection, Transform; its main outputs are Instances. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Instances	instances	Geometry3D
Selection	selection	Bool
Transform	transform	Matrix

Outputs

Socket	Key	Type
Instances	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Selection	selection	Bool	Inputs	1.0
Translation X	translationX	Float	Inputs	0.0
Translation Y	translationY	Float	Inputs	0.0
Translation Z	translationZ	Float	Inputs	0.0
Rotation X	rotationX	Float	Inputs	0.0
Rotation Y	rotationY	Float	Inputs	0.0
Rotation Z	rotationZ	Float	Inputs	0.0
Scale X	scaleX	Float	Inputs	1.0
Scale Y	scaleY	Float	Inputs	1.0
Scale Z	scaleZ	Float	Inputs	1.0

How to use it

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

• Set Grid Transform — geometry.set_grid_transform
• Bevel Faces — geometry.bevel_faces
• Bounding Box — geometry.bounding_box
• Curve to Mesh — geometry.curve_to_mesh
• Deactivate Voxels — geometry.grid_deactivate_voxels

Return to the complete Oraphim node reference.