How to use Combine Particle Fields node in Oraphim

Type ID: motion.particles.force_combine
Category: Particles

What this node does

Performs the combine particle fields stage of a particle workflow.

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

Inputs

Socket	Key	Type
Field A	in_field_a	Field
Field B	in_field_b	Field

Outputs

Socket	Key	Type
Field	out_field	Field

Controls

Control	Key	Type	Group	Registry default
Evaluation Order	order	String	Combine	0.0
Field A Weight	weightA	Float	Combine	1.0
Field B Weight	weightB	Float	Combine	1.0
Enable Field A	enabledA	Bool	Combine	1.0
Enable Field B	enabledB	Bool	Combine	1.0

How to use it

1. Add Combine Particle Fields from node search. Use motion.particles.force_combine when you need the exact registry entry.
2. Connect a compatible Field source to Field A. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Evaluation Order, Field A Weight, Field B Weight 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 Combine Particle Fields. Feed a compatible source into Field A. Change Evaluation Order 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

• Particle Force Field — motion.particles.force_field
• Particle Solver — motion.particles.solver
• Particle Source — motion.particles.emitter
• Cloth System — motion.simulation.cloth
• Fluid System — motion.simulation.fluid

Return to the complete Oraphim node reference.