What causes a ground-check raycast giving false negatives on platform edges?

A single raycast from the capsule center misses the floor when the player stands near an edge so part of the foot is over the gap, even though they are clearly supported.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a Ground-Check Raycast Returning False on Platform Edges

Quick answer: Replace the single center ray with a small spherecast or several offset rays under the foot so any contact within the foot radius counts as grounded.

A center-only ground ray flickers to airborne when the player toes a ledge, triggering fall animations and broken jumps. Probe a wider footprint. Here is how.

How to fix it

1. Use a spherecast or capsule cast

Cast a sphere matching the foot radius downward instead of a thin ray. It registers ground as long as any part of the footprint is supported, which matches how the character actually stands.

2. Or use multiple offset rays

Fire several rays at the center and the edges of the foot. Treat the player as grounded if any of them hit within the ground tolerance distance, eliminating the single-point blind spot.

3. Tune the cast length and origin

Start the cast slightly inside the capsule and extend it a little past the foot so a grounded player reliably registers without the cast reaching distant geometry below.

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.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.