Node reference

How to use Cloth System node in Oraphim

Use the Cloth System node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID motion.simulation.cloth.

Updated August 28, 2026

How to use Cloth System node in Oraphim

Type ID: motion.simulation.cloth
Category: Particles

What this node does

Runs the cloth system stage in a procedural motion graph.

The current Oraphim runtime registers 6 sockets and 34 properties for this node. Its main registered inputs are Surface Geometry, Collision Geometry, Collision Constraint; its main outputs are Deformed Surface, Simulation, Metadata. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

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

Outputs

Socket Key Type
Deformed Surface out_geometry Geometry3D
Simulation out_simulation Simulation
Metadata out_metadata Metadata

Controls

Control Key Type Group Registry default
Surface Source sourceMode String Source Built-in Grid
Width width Float Source 8.0
Height height Float Source 6.0
Resolution X segmentsX Int Source 24.0
Resolution Y segmentsY Int Source 18.0
Pinning pinMode String Setup Top Edge
Start Time startTime Float Setup 0.0
Time Scale timeScale Float Solver 1.0
Quality quality String Solver Interactive
Substeps substeps Int Solver 4.0
Constraint Iterations iterations Int Solver 8.0
Damping damping Float Solver 0.03500000014901161
Surface Mass mass Float Solver 1.0
Stretch Stiffness stretchStiffness Float Material 0.9200000166893005
Shear Stiffness shearStiffness Float Material 0.7200000286102295
Bend Stiffness bendStiffness Float Material 0.2800000011920929
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 1.0
Wind Y windY Float Forces 0.0
Wind Z windZ Float Forces 0.25
Wind Strength windStrength Float Forces 0.0
Wind Turbulence turbulence Float Forces 0.0
Collisions collisionEnabled Bool Collision 1.0
Collision Thickness collisionThickness Float Collision 0.05000000074505806
Collision Friction collisionFriction Float Collision 0.18000000715255737
Collision Bounce collisionBounce Float Collision 0.05000000074505806
Floor floorEnabled Bool Collision 0.0
Floor Height floorHeight Float Collision -4.0
Self Collision selfCollision Bool Collision 0.0
Self Collision Distance selfCollisionDistance Float Collision 0.07999999821186066
Seed seed Int Forces 1.0
Cache Mode cacheMode String Cache Memory

How to use it

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

Return to the complete Oraphim node reference.