How to use Volume Field / Forces node in Oraphim

Type ID: motion.volume.field
Category: Utility

What this node does

The Volume Field / Forces node is registered in Oraphim's Utility category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 4 sockets and 26 properties for this node. Its main registered inputs are Source, Volume; its main outputs are Field, Volume. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Source	in_source	Metadata
Volume	in_volume	Volume

Outputs

Socket	Key	Type
Field	out_field	Field
Volume	out_volume	Volume

Controls

Control	Key	Type	Group	Registry default
Turbulence	turbulence	Float	Field	0.0
Buoyancy	buoyancy	Float	Field	0.0
Gravity	gravity	Float	Field	0.0
Wind Speed	windSpeed	Float	Wind	0.0
Wind X	windX	Float	Wind	1.0
Wind Y	windY	Float	Wind	0.0
Wind Z	windZ	Float	Wind	0.0
Curl Strength	curlStrength	Float	Curl	0.0
Curl Frequency	curlFrequency	Float	Curl	2.0
Curl Scale	curlScale	Float	Curl	1.0
Vorticity	vorticity	Float	Curl	0.0
Spiral Strength	spiralStrength	Float	Curl	0.0
Lift	lift	Float	Velocity	0.0
Swirl	swirl	Float	Velocity	0.0
Radial	radial	Float	Velocity	0.0
Drag	drag	Float	Velocity	0.0
Randomization	velocityRandomization	Float	Velocity	0.0
Chaos	velocityChaos	Float	Velocity	0.0
Density Lift	smokeLift	Float	Combustion	0.0
Temperature Lift	fireLift	Float	Combustion	0.0
Dissipation	dissipation	Float	Simulation	0.0
Time Scale	timeScale	Float	Simulation	1.0
Simulation Speed	simulationSpeed	Float	Simulation	1.0
Substeps	simulationSubsteps	Int	Simulation	1.0
Solver Iterations	solverIterations	Int	Simulation	4.0
Pressure Iterations	pressureIterations	Int	Simulation	8.0

How to use it

1. Add Volume Field / Forces from node search. Use motion.volume.field when you need the exact registry entry.
2. Connect a compatible Metadata source to Source. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Turbulence, Buoyancy, Gravity first so you can see the node's effect in isolation.
4. Route Field (Field) 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 Field / Forces. Feed a compatible source into Source. Change Turbulence away from its registry default and compare the result. Connect Field 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 Material — motion.volume.material
• Volume Source / SDF — motion.volume.source
• Attribute Map — motion.geometry.attribute_map
• Boolean Math — motion.logic.boolean

Return to the complete Oraphim node reference.