Quick answer: Use one consistent slope-angle source and one comparison; if the floor angle exceeds the walkable limit, force a downhill slide instead of treating it as standable ground.

At the exact slope limit a character should begin sliding, not stick. Mismatched checks leave a dead zone. Unify the angle test. Here is how.

How to fix it

1. Measure the slope angle once

Compute the floor angle from the ground hit normal a single time per frame and reuse it for both the grounded decision and the slide decision so they cannot disagree at the boundary.

2. Slide when angle > limit

If the floor angle is greater than the walkable limit, project gravity along the slope and add that as a downhill velocity each frame. Below the limit, treat the surface as standable and apply friction.

3. Avoid double epsilons

Use the same tolerance everywhere. A grounded check with a generous epsilon plus a strict slide check creates a band of angles where the player is grounded but never slides.

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 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.

A crash you can name from its stack trace is a crash you can usually fix in minutes.