From 9352d77c923bc42e1a87de6e93ec5757901bbd1e Mon Sep 17 00:00:00 2001 From: NepDisk Date: Fri, 12 Sep 2025 01:29:08 -0400 Subject: [PATCH] 'Increment move resolution increase' cherry-pick https://gitlab.com/kart-krew-dev/ring-racers/-/commit/adbdc63895e0955cee565097222859a6cee86572 --- src/p_map.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/p_map.c b/src/p_map.c index d258de3c9..18ccad183 100644 --- a/src/p_map.c +++ b/src/p_map.c @@ -2543,7 +2543,7 @@ increment_move radius = max(radius, mapobjectscale); // And Big Large (tm) movements can skip over slopes. - radius = min(radius, 16*mapobjectscale); + radius = min(radius, 8*mapobjectscale); // (This whole "step" system is flawed; it was OK before, but the addition of slopes has // exposed the problems with doing it like this. The right thing to do would be to use