How to use Volume Cube node in Oraphim

Type ID: geometry.volume_cube
Category: Generator

What this node does

The Volume Cube node is registered in Oraphim's Generator category and performs the graph operation represented by its sockets and controls below.

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

Inputs

Socket	Key	Type
Density	density	Float
Background	background	Float
Min	min	Vector3
Max	max	Vector3
Resolution X	resolutionX	Int
Resolution Y	resolutionY	Int
Resolution Z	resolutionZ	Int

Outputs

Socket	Key	Type
Volume	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Density	density	Float	Inputs	1.0
Background	background	Float	Inputs	0.0
Min X	minX	Float	Inputs	-1.0
Min Y	minY	Float	Inputs	-1.0
Min Z	minZ	Float	Inputs	-1.0
Max X	maxX	Float	Inputs	1.0
Max Y	maxY	Float	Inputs	1.0
Max Z	maxZ	Float	Inputs	1.0
Resolution X	resolutionX	Int	Inputs	32.0
Resolution Y	resolutionY	Int	Inputs	32.0
Resolution Z	resolutionZ	Int	Inputs	32.0

How to use it

1. Add Volume Cube from node search. Use geometry.volume_cube when you need the exact registry entry.
2. Connect a compatible Float source to Density. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Density, Background, Min X 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 Volume Cube. Feed a compatible source into Density. 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

• Arc — geometry.curve_primitive_arc
• Cone — geometry.mesh_primitive_cone
• Curve Circle — geometry.curve_primitive_circle
• Cylinder — geometry.mesh_primitive_cylinder
• Distribute Points in Grid — geometry.distribute_points_in_grid

Return to the complete Oraphim node reference.