Quick answer: Increase floor_snap_length to exceed the worst-case per-frame drop, keep floor_stop_on_slope appropriate, and ensure the body stays in floor mode rather than free fall.

Running fast downhill in Godot, a CharacterBody3D can pop off the ground each frame if snap cannot bridge the gap. Lengthen the snap. Here is how.

How to fix it

1. Raise floor_snap_length

Set floor_snap_length long enough to cover the vertical distance the body would fall in one frame at top downhill speed, so the snap reattaches to the slope instead of letting the body sail off.

2. Keep up_direction correct

Confirm up_direction is set (usually Vector3.UP) so move_and_slide knows which surfaces are floors and applies snapping to them rather than treating the slope as a wall.

3. Tune max floor angle

Make sure floor_max_angle covers the slope so the surface still counts as a floor at speed; if the slope exceeds it the body treats it as non-floor and will not snap.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.