Node reference

How to use Index of Nearest node in Oraphim

Use the Index of Nearest node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.index_of_nearest.

Updated August 28, 2026

How to use Index of Nearest node in Oraphim

Type ID: geometry.index_of_nearest
Category: Utility

What this node does

The Index of Nearest node is registered in Oraphim's Utility category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 4 sockets and 2 properties for this node. Its main registered inputs are Position, Group ID; its main outputs are Index, Has Neighbor. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Position position Vector3
Group ID groupId Int

Outputs

Socket Key Type
Index index Int
Has Neighbor hasNeighbor Bool

Controls

Control Key Type Group Registry default
Position position Vector3 Inputs 0.0
Group ID groupId Int Inputs 0.0

How to use it

  1. Add Index of Nearest from node search. Use geometry.index_of_nearest 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, Group ID first so you can see the node's effect in isolation.
  4. Route Index (Int) 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 Index of Nearest. Feed a compatible source into Position. Change Position away from its registry default and compare the result. Connect Index 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.