How to use Simulation Cache node in Oraphim

Type ID: motion.simulation.cache
Category: Particles

What this node does

Runs the simulation cache stage in a procedural motion graph.

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

Inputs

Socket	Key	Type
Particles	in_particles	Particle
Volume	in_volume	Volume
Simulation	in_simulation	Simulation

Outputs

Socket	Key	Type
Particles	out_particles	Particle
Volume	out_volume	Volume
Simulation	out_simulation	Simulation
Cache Status	out_cache	Cache

Controls

Control	Key	Type	Group	Registry default
Cache Mode	cacheMode	String	Cache	Memory
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 Simulation Cache from node search. Use motion.simulation.cache 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 Cache Mode, Cache FPS (0 = Composition), Memory Frame Limit 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 Simulation Cache. Feed a compatible source into Particles. Change Cache Mode 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

• Fluid System — motion.simulation.fluid
• Cloth System — motion.simulation.cloth
• Rigid Body System — motion.simulation.rigid_body
• Geometry Collider — motion.simulation.collider
• Particle Solver — motion.particles.solver

Return to the complete Oraphim node reference.