How to use Volume Source / SDF node in Oraphim

Type ID: motion.volume.source
Category: Generator

What this node does

The Volume Source / SDF 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 3 sockets and 28 properties for this node. Its main registered inputs are Geometry; its main outputs are Source, Volume. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Geometry	in_geometry	Geometry3D

Outputs

Socket	Key	Type
Source	out_source	Metadata
Volume	out_volume	Volume

Controls

Control	Key	Type	Group	Registry default
Source Type	sourceType	String	Source	Auto
Interpret As	sourceRole	String	Source	0.0
Role Strength	sourceRoleStrength	Float	Source	1.0
Boundary Width	sourceBoundaryWidth	Float	Source	0.11999999731779099
Influence Radius	sourceInfluenceRadius	Float	Source	0.44999998807907104
Attribute Strength	sourceAttributeStrength	Float	Source	0.0
Geometry Samples	sampleLimit	Int	Source	384.0
Boolean	booleanOperation	String	Source	0.0
Position X	positionX	Float	Transform	0.0
Position Y	positionY	Float	Transform	0.0
Position Z	positionZ	Float	Transform	0.0
Rotation X	rotationX	Float	Transform	0.0
Rotation Y	rotationY	Float	Transform	0.0
Rotation Z	rotationZ	Float	Transform	0.0
Pivot X	pivotX	Float	Transform	0.0
Pivot Y	pivotY	Float	Transform	0.0
Pivot Z	pivotZ	Float	Transform	0.0
Scale X	scaleX	Float	Transform	1.0
Scale Y	scaleY	Float	Transform	1.0
Scale Z	scaleZ	Float	Transform	1.0
Radius	radius	Float	Shape	0.6200000047683716
Secondary Radius	secondaryRadius	Float	Shape	0.18000000715255737
Size X	sizeX	Float	Shape	0.75
Size Y	sizeY	Float	Shape	0.75
Size Z	sizeZ	Float	Shape	0.75
Surface Radius	thickness	Float	Shape	0.07999999821186066
Smoothness	smoothness	Float	Shape	0.11999999731779099
Falloff	falloff	Float	Shape	0.23999999463558197

How to use it

1. Add Volume Source / SDF from node search. Use motion.volume.source when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Geometry. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Source Type, Interpret As, Role Strength first so you can see the node's effect in isolation.
4. Route Source (Metadata) 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 Source / SDF. Feed a compatible source into Geometry. Change Source Type away from its registry default and compare the result. Connect Source 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

• Volume System — motion.volume.builder
• Volume Field / Forces — motion.volume.field
• Volume Material — motion.volume.material
• Bar Chart Generator — motion.chart.bar
• Data Chart — motion.chart.data

Return to the complete Oraphim node reference.