Node reference

How to use Sample Nearest Surface node in Oraphim

Use the Sample Nearest Surface node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.sample_nearest_surface.

Updated August 28, 2026

How to use Sample Nearest Surface node in Oraphim

Type ID: geometry.sample_nearest_surface
Category: Utility

What this node does

Samples nearest surface data for downstream field or geometry operations.

The current Oraphim runtime registers 7 sockets and 5 properties for this node. Its main registered inputs are Mesh, Value, Group ID; its main outputs are Value, Is Valid. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Mesh mesh Geometry3D
Value value Float
Group ID groupId Int
Sample Position samplePosition Vector3
Sample Group ID sampleGroupId Int

Outputs

Socket Key Type
Value outValue Float
Is Valid isValid Bool

Controls

Control Key Type Group Registry default
Group ID groupId Int Inputs 0.0
Sample Position samplePosition Vector3 Inputs 0.0
Sample Group ID sampleGroupId Int Inputs 0.0
Value value Float Inputs 0.0
Data Type data_type String Node FLOAT

How to use it

  1. Add Sample Nearest Surface from node search. Use geometry.sample_nearest_surface when you need the exact registry entry.
  2. Connect a compatible Geometry3D source to Mesh. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Group ID, Sample Position, Sample Group ID 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 Nearest Surface. Feed a compatible source into Mesh. Change Group ID 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.