How to use Distribute Points in Volume node in Oraphim

Type ID: geometry.distribute_points_in_volume
Category: Generator

What this node does

The Distribute Points in Volume 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 7 sockets and 8 properties for this node. Its main registered inputs are Volume, Mode, Density; its main outputs are Points. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Volume	volume	Geometry3D
Mode	mode	Menu
Density	density	Float
Seed	seed	Int
Spacing	spacing	Vector3
Threshold	threshold	Float

Outputs

Socket	Key	Type
Points	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Mode	mode	Menu	Inputs	Random
Density	density	Float	Inputs	1.0
Seed	seed	Int	Inputs	0.0
Spacing X	spacingX	Float	Inputs	0.30000001192092896
Spacing Y	spacingY	Float	Inputs	0.30000001192092896
Spacing Z	spacingZ	Float	Inputs	0.30000001192092896
Threshold	threshold	Float	Inputs	0.10000000149011612
Radius	radius	Float	Inputs	0.05000000074505806

How to use it

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