Quick answer: Raise the friction curve stiffness, increase extremum/asymptote slip values, and make sure the wheel suspension keeps the tire loaded against the ground.

A car that climbs flat ground fine but spins its wheels on a ramp is almost always a friction curve problem. WheelCollider grip is driven by the slip-vs-force curves, and the defaults are tuned for gentle slopes. Here is how to fix it.

How to fix it

1. Stiffen the friction curves

On the WheelCollider, raise forwardFriction.stiffness and sidewaysFriction.stiffness (try 2-3) so the tire produces more force at the same slip. This directly increases available grip on inclines.

2. Tune the slip points

Increase extremumSlip and extremumValue so peak grip happens at a higher slip, and raise asymptoteValue so the tire keeps useful force after the peak instead of breaking loose.

3. Keep the tire loaded

Make sure suspension spring and damper hold the wheel against the slope; a wheel that unloads on a bump produces zero friction. Check WheelHit.force at runtime to confirm the tire stays in contact.

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