How to use Fluid System node in Oraphim

Type ID: motion.simulation.fluid
Category: Particles

What this node does

Runs the fluid system stage in a procedural motion graph.

The current Oraphim runtime registers 8 sockets and 41 properties for this node. Its main registered inputs are Source Geometry, Collision Geometry, Collision Constraint; its main outputs are Fluid Geometry, Particles, Volume. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Source Geometry	in_geometry	Geometry3D
Collision Geometry	in_collision	Geometry3D
Collision Constraint	in_constraint	Constraint

Outputs

Socket	Key	Type
Fluid Geometry	out_geometry	Geometry3D
Particles	out_particles	Particle
Volume	out_volume	Volume
Simulation	out_simulation	Simulation
Metadata	out_metadata	Metadata

Controls

Control	Key	Type	Group	Registry default
Phase	phase	String	Source	Liquid
Source	sourceMode	String	Source	Box
Output	representation	String	Output	Hybrid
Size X	sizeX	Float	Domain	6.0
Size Y	sizeY	Float	Domain	6.0
Size Z	sizeZ	Float	Domain	6.0
Position X	positionX	Float	Domain	0.0
Position Y	positionY	Float	Domain	0.0
Position Z	positionZ	Float	Domain	0.0
Particle Resolution	particleResolution	Int	Resolution	12.0
Volume Resolution	volumeResolution	Int	Resolution	40.0
Maximum Particles	maxParticles	Int	Resolution	12000.0
Particle Radius	particleRadius	Float	Surface	0.11999999731779099
Surface Smoothing	surfaceSmoothing	Float	Surface	0.6499999761581421
Start Time	startTime	Float	Solver	0.0
Time Scale	timeScale	Float	Solver	1.0
Quality	quality	String	Solver	Interactive
Substeps	substeps	Int	Solver	3.0
Pressure Iterations	iterations	Int	Solver	5.0
Rest Density	restDensity	Float	Liquid	1.0
Pressure	pressure	Float	Liquid	1.2000000476837158
Viscosity	viscosity	Float	Liquid	0.07999999821186066
Surface Tension	surfaceTension	Float	Liquid	0.11999999731779099
Vorticity	vorticity	Float	Forces	0.0
Velocity Damping	damping	Float	Solver	0.014999999664723873
Gravity X	gravityX	Float	Forces	0.0
Gravity Y	gravityY	Float	Forces	-9.8100004196167
Gravity Z	gravityZ	Float	Forces	0.0
Wind X	windX	Float	Forces	0.0
Wind Y	windY	Float	Forces	0.0
Wind Z	windZ	Float	Forces	0.0
Turbulence	turbulence	Float	Forces	0.0
Buoyancy	buoyancy	Float	Gas	0.75
Dissipation	dissipation	Float	Gas	0.11999999731779099
Temperature	temperature	Float	Gas	0.5
Boundary	boundaryMode	String	Collision	Closed
Collisions	collisionEnabled	Bool	Collision	1.0
Collision Friction	collisionFriction	Float	Collision	0.07999999821186066
Collision Bounce	collisionBounce	Float	Collision	0.20000000298023224
Seed	seed	Int	Solver	1.0
Cache Mode	cacheMode	String	Cache	Memory

How to use it

1. Add Fluid System from node search. Use motion.simulation.fluid when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Source Geometry. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Phase, Source, Output first so you can see the node's effect in isolation.
4. Route Fluid Geometry (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 Fluid System. Feed a compatible source into Source Geometry. Change Phase away from its registry default and compare the result. Connect Fluid Geometry 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

• Cloth System — motion.simulation.cloth
• Rigid Body System — motion.simulation.rigid_body
• Simulation Cache — motion.simulation.cache
• Geometry Collider — motion.simulation.collider
• Particle Solver — motion.particles.solver

Return to the complete Oraphim node reference.