Node reference

How to use Instances to Points node in Oraphim

Use the Instances to Points node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.instances_to_points.

Updated August 28, 2026

How to use Instances to Points node in Oraphim

Type ID: geometry.instances_to_points
Category: Transform

What this node does

The Instances to Points 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 2 properties for this node. Its main registered inputs are Instances, Selection, Position; its main outputs are Points. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Instances instances Geometry3D
Selection selection Bool
Position position Vector3
Radius radius Float

Outputs

Socket Key Type
Points out_geometry Geometry3D

Controls

Control Key Type Group Registry default
Selection selection Bool Inputs 1.0
Radius radius Float Inputs 0.05000000074505806

How to use it

  1. Add Instances to Points from node search. Use geometry.instances_to_points 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, Radius first so you can see the node's effect in isolation.
  4. Route Points (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 Instances to Points. Feed a compatible source into Instances. Change Selection away from its registry default and compare the result. Connect Points 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.

Return to the complete Oraphim node reference.