Rapier body and joint stability
Investigates shaking stacks, exploding joints and objects passing through walls. It checks scale, mass and collision geometry before increasing solver effort or changing the physical behavior of the game.
rapier-bodies-joints-stability
See how it helpsWhen is it useful?
Use it when stacks shake, joints stretch or fast objects pass through geometry under representative gameplay load.
What does it help you do?
- Checks scale, body type, mass and collision geometry first.
- Defines joint anchors and intended degrees of freedom.
- Uses continuous collision detection only for measured tunneling.
Try asking this
Our warehouse puzzle has a crane lifting stacked crates. Diagnose a swinging joint that launches the load and a fast crate that crosses a thin wall. Record scale, anchors and body settings, then compare the same lift after a targeted correction.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Rapier — bodies joints stability
Use when tuning Rapier masses, constraints, CCD, solver iterations or unstable stacks.
Version and project gate
Inspect Rust crate features or JS/WASM package and version, 2D/3D choice, framework wrapper version, units, solver settings, timestep ownership, body/collider handles and render synchronization. Determinism depends on binding, version, initialization and operation order. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Check scale, body type, mass/inertia and collision geometry before increasing solver work. Define the intended degrees of freedom and local anchors for each joint. Enable CCD only for a demonstrated tunneling problem and measure its cost. Keep visual and collider geometry roles explicit.
Deliver
A stability diagnosis and the smallest body/constraint adjustment that preserves gameplay. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Extreme scale/mass ratios or contradictory constraints are not reliably fixed by maximum solver iterations.
Acceptance scenario
Reproduce the worst stack or joint load, a high-speed impact, sleep/wake and a reset with the same input sequence. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Vector. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md