How to use Mesh to Volume node in Oraphim

Type ID: geometry.mesh_to_volume
Category: Transform

What this node does

Converts incoming data with the Mesh to Volume operation for use later in the graph.

The current Oraphim runtime registers 7 sockets and 5 properties for this node. Its main registered inputs are Mesh, Density, Resolution Mode; its main outputs are Volume. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Mesh	mesh	Geometry3D
Density	density	Float
Resolution Mode	resolutionMode	String
Voxel Size	voxelSize	Float
Voxel Amount	voxelAmount	Float
Interior Band Width	interiorBandWidth	Float

Outputs

Socket	Key	Type
Volume	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Density	density	Float	Inputs	1.0
Resolution Mode	resolutionMode	String	Inputs	0.0
Voxel Size	voxelSize	Float	Inputs	0.30000001192092896
Voxel Amount	voxelAmount	Float	Inputs	64.0
Interior Band Width	interiorBandWidth	Float	Inputs	0.20000000298023224

How to use it

1. Add Mesh to Volume from node search. Use geometry.mesh_to_volume 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 Density, Resolution Mode, Voxel Size first so you can see the node's effect in isolation.
4. Route Volume (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 to Volume. Feed a compatible source into Mesh. Change Density away from its registry default and compare the result. Connect Volume 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

• Clone Elements — geometry.clone_elements
• Fillet Curve — geometry.curve_fillet
• Layout Elements — geometry.layout_elements
• Motion Constraint — geometry.motion_constraint
• Motion FX — geometry.motion_fx

Return to the complete Oraphim node reference.