How to use Translate Instances node in Oraphim

Type ID: geometry.translate_instances
Category: Transform

What this node does

The Translate Instances 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 5 sockets and 5 properties for this node. Its main registered inputs are Instances, Selection, Translation; 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
Translation	translation	Vector3
Local Space	localSpace	Bool

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
Local Space	localSpace	Bool	Inputs	1.0

How to use it

1. Add Translate Instances from node search. Use geometry.translate_instances 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 Translate Instances. 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

• Bounding Box — geometry.bounding_box
• Extrude Mesh — geometry.extrude_mesh
• Instance on Points — geometry.instance_on_points
• Instances to Points — geometry.instances_to_points
• Mesh to Points — geometry.mesh_to_points

Return to the complete Oraphim node reference.