How to use Particle Force Field node in Oraphim

Type ID: motion.particles.force_field
Category: Particles

What this node does

Performs the particle force field stage of a particle workflow.

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

Inputs

Socket	Key	Type
Particles	in_particles	Particle
Influence Geometry	in_geometry	Geometry3D

Outputs

Socket	Key	Type
Particles	out_particles	Particle
Field	out_field	Field

Controls

Control	Key	Type	Group	Registry default
Enabled	enabled	Bool	Field	1.0
Field Type	fieldType	String	Field	0.0
Strength	strength	Float	Field	100.0
Weight	weight	Float	Field	1.0
Blend Mode	blendMode	String	Field	0.0
Direction X	directionX	Float	Direction	1.0
Direction Y	directionY	Float	Direction	0.0
Direction Z	directionZ	Float	Direction	0.0
Center X	centerX	Float	Position	0.5
Center Y	centerY	Float	Position	0.5
Center Z	centerZ	Float	Position	0.0
Radius	radius	Float	Falloff	0.0
Falloff	falloff	Float	Falloff	1.0
Noise Scale	noiseScale	Float	Noise	0.009999999776482582
Seed	seed	Int	Noise	1.0
Custom X	customX	Float	Custom Vector	0.0
Custom Y	customY	Float	Custom Vector	0.0
Custom Z	customZ	Float	Custom Vector	0.0

How to use it

1. Add Particle Force Field from node search. Use motion.particles.force_field 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 Enabled, Field Type, Strength 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 Force Field. Feed a compatible source into Particles. Change Enabled 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 Solver — motion.particles.solver
• Particle Source — motion.particles.emitter
• Combine Particle Fields — motion.particles.force_combine
• Fluid System — motion.simulation.fluid
• Cloth System — motion.simulation.cloth

Return to the complete Oraphim node reference.