How to use Particle Solver node in Oraphim

Type ID: motion.particles.solver
Category: Particles

What this node does

Performs the particle solver stage of a particle workflow.

The current Oraphim runtime registers 5 sockets and 14 properties for this node. Its main registered inputs are Particles, Field, Constraint; its main outputs are Particles, Simulation. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Particles	in_particles	Particle
Field	in_field	Field
Constraint	in_constraint	Constraint

Outputs

Socket	Key	Type
Particles	out_particles	Particle
Simulation	out_simulation	Simulation

Controls

Control	Key	Type	Group	Registry default
Integrator	integrator	String	Solver	0.0
Substeps	substeps	Int	Solver	2.0
Maximum Step	maxStepSeconds	Float	Solver	0.03333299979567528
Time Scale	timeScale	Float	Time	1.0
Start Time	startTime	Float	Time	0.0
Warm Start	warmStart	Bool	Time	0.0
Collision Bounce	surfaceBounce	Float	Collision	0.5
Collision Friction	surfaceFriction	Float	Collision	0.10000000149011612
Deterministic Birth Order	deterministic	Bool	Solver	1.0
Simulation Backend	simulationBackend	String	Solver	0.0
Cache Mode	cacheMode	String	Cache	0.0
Cache FPS (0 = Composition)	cacheFrameRate	Int	Cache	0.0
Memory Frame Limit	cacheMemoryFrames	Int	Cache	120.0
Cache Namespace	cacheNamespace	String	Cache	Auto

How to use it

1. Add Particle Solver from node search. Use motion.particles.solver when you need the exact registry entry.
2. Connect a compatible Particle source to Particles. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Integrator, Substeps, Maximum Step first so you can see the node's effect in isolation.
4. Route Particles (Particle) 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 Particle Solver. Feed a compatible source into Particles. Change Integrator away from its registry default and compare the result. Connect Particles 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

• Particle Force Field — motion.particles.force_field
• Combine Particle Fields — motion.particles.force_combine
• Particle Source — motion.particles.emitter
• Fluid System — motion.simulation.fluid
• Cloth System — motion.simulation.cloth

Return to the complete Oraphim node reference.