Node reference

How to use Sample Grid Index node in Oraphim

Use the Sample Grid Index node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.sample_grid_index.

Updated August 28, 2026

How to use Sample Grid Index node in Oraphim

Type ID: geometry.sample_grid_index
Category: Utility

What this node does

Samples grid index data for downstream field or geometry operations.

The current Oraphim runtime registers 5 sockets and 4 properties for this node. Its main registered inputs are Grid, X, Y; its main outputs are Value. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Grid grid Grid
X x Int
Y y Int
Z z Int

Outputs

Socket Key Type
Value value Float

Controls

Control Key Type Group Registry default
X x Int Inputs 0.0
Y y Int Inputs 0.0
Z z Int Inputs 0.0
Data Type data_type String Node FLOAT

How to use it

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