Node reference

How to use SDF Grid Boolean node in Oraphim

Use the SDF Grid Boolean node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.sdf_grid_boolean.

Updated August 28, 2026

How to use SDF Grid Boolean node in Oraphim

Type ID: geometry.sdf_grid_boolean
Category: Transform

What this node does

Processes grid, volume, or SDF data with the SDF Grid Boolean operation.

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

Inputs

Socket Key Type
Grid 1 grid1 Geometry3D
Grid grid Geometry3D
Grid 2 grid2 Geometry3D

Outputs

Socket Key Type
Grid out_geometry Geometry3D

Controls

Control Key Type Group Registry default
Operation operation String Node 0.0

How to use it

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