What causes projecting velocity onto a slope plane in Godot?

Moving with a flat horizontal velocity on an inclined surface either pushes into the slope or floats off it, because the velocity is not constrained to the plane defined by the surface normal.

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 Projecting Velocity onto a Slope Plane in Godot

Quick answer: Project the velocity onto the slope by subtracting its component along the normal: v -= n * v.dot(n), which keeps speed tangent to the surface.

A character that slows down going up ramps or slides oddly across slopes is moving without projecting onto the surface plane. Removing the normal component fixes slope movement. Here is how.

How to fix it

1. Subtract the normal component

Given a surface normal n from get_floor_normal(), compute velocity = velocity - n * velocity.dot(n) so the velocity lies in the slope plane and keeps its magnitude tangentially.

2. Reproject after each step

Recompute the projection each frame because the floor normal changes as the character crosses between surfaces of different inclines.

3. Use slide for collisions

Combine the projection with move_and_slide(), which already deflects along collision normals, so you only project the input direction before passing it in.

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.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.