domains / families / software-engineering / physics-tuning

physics-tuning

separate

Tune game physics for stable, good-feeling motion — fixed vs variable timestep, render interpolation, mass/gravity/drag, continuous collision detection (CCD) to stop tunneling, fixing jitter, and collision layers/masks. Engine-neutral. Use when the user mentions physics feel, jitter, tunneling, fixed timestep, FixedUpdate, CCD, bouncing/unstable physics, or collision layers.

When to use

• Use when motion jitters, objects pass through walls (tunneling), stacks
• Use to decide what goes in the fixed (physics) step vs the render frame, and
• Use to tune gravity, mass, drag, restitution, solver iterations, sleeping, and

When not to use

• engine-specific physics nodes or components
• collision callbacks implementation
• movement decisions like jumping or AI steering
• platformer jump-feel specifics like coyote time
• input or controller logic

Skill page

Source