How to use Mesh Boolean node in Oraphim (geometry.mesh_boolean)

Type ID: geometry.mesh_boolean
Category: Transform

What this node does

The Mesh Boolean node is registered in Oraphim's Transform category and performs the graph operation represented by its sockets and controls below.

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

Inputs

Socket	Key	Type
Mesh 1	mesh1	Geometry3D
Mesh 2	mesh2	Geometry3D
Self Intersection	selfIntersection	Bool
Hole Tolerant	holeTolerant	Bool

Outputs

Socket	Key	Type
Mesh	out_geometry	Geometry3D
Intersecting Edges	intersectingEdges	Bool

Controls

Control	Key	Type	Group	Registry default
Operation	operation	Menu	Inputs	INTERSECT
Solver	solver	Menu	Inputs	FLOAT
Self Intersection	selfIntersection	Bool	Inputs	0.0
Hole Tolerant	holeTolerant	Bool	Inputs	0.0

How to use it

1. Add Mesh Boolean from node search. Use geometry.mesh_boolean when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Mesh 1. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Operation, Solver, Self Intersection first so you can see the node's effect in isolation.
4. Route Mesh (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 Mesh Boolean. Feed a compatible source into Mesh 1. Change Operation away from its registry default and compare the result. Connect Mesh 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
• Bounding Box — geometry.bounding_box
• Curve to Mesh — geometry.curve_to_mesh
• Deactivate Voxels — geometry.grid_deactivate_voxels
• Delete Geometry — geometry.delete_geometry

Return to the complete Oraphim node reference.