How to use Clip Grid node in Oraphim

Type ID: geometry.grid_clip
Category: Transform

What this node does

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

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

Inputs

Socket	Key	Type
Grid	grid	Geometry3D
Min X	minX	Int
Min Y	minY	Int
Min Z	minZ	Int
Max X	maxX	Int
Max Y	maxY	Int
Max Z	maxZ	Int

Outputs

Socket	Key	Type
Grid	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Data Type	dataType	String	Node	0.0
Min X	minX	Int	Inputs	0.0
Min Y	minY	Int	Inputs	0.0
Min Z	minZ	Int	Inputs	0.0
Max X	maxX	Int	Inputs	32.0
Max Y	maxY	Int	Inputs	32.0
Max Z	maxZ	Int	Inputs	32.0

How to use it

1. Add Clip Grid from node search. Use geometry.grid_clip when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Grid. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Data Type, Min X, Min Y 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 Clip Grid. Feed a compatible source into Grid. Change Data Type 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.

Related nodes

• Bevel Faces — geometry.bevel_faces
• Clone Elements — geometry.clone_elements
• Curve to Points — geometry.curve_to_points
• Duplicate Elements — geometry.duplicate_elements
• Edge Paths to Curves — geometry.edge_paths_to_curves

Return to the complete Oraphim node reference.