How to use Geometry Collider node in Oraphim

Type ID: motion.simulation.collider
Category: Particles

What this node does

Runs the geometry collider stage in a procedural motion graph.

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

Inputs

Socket	Key	Type
Geometry	in_geometry	Geometry3D

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D
Constraint	out_constraint	Constraint

Controls

Control	Key	Type	Group	Registry default
Enabled	enabled	Bool	Collision	1.0
Collision Thickness	thickness	Float	Collision	0.0
Bounce	bounce	Float	Response	0.5
Friction	friction	Float	Response	0.10000000149011612
Stickiness	stickiness	Float	Response	0.0

How to use it

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

• Cloth System — motion.simulation.cloth
• Fluid System — motion.simulation.fluid
• Rigid Body System — motion.simulation.rigid_body
• Simulation Cache — motion.simulation.cache
• Particle Force Field — motion.particles.force_field

Return to the complete Oraphim node reference.