Fix: Unity Splines Package Walker Stuttering at Low Speed

Here is how to fix Unity Splines package walkers that stutter, jitter, or move at uneven speeds along a curve. Your follower advances smoothly along straight sections, then visibly slows or jumps in tighter curves. The issue is the parameterization: t goes 0→1 across the whole spline, but a unit of t in a tight curve covers far less world space than the same t on a straight section.

The Symptom

An object follows a spline using the Splines package. At normal speed (5+ m/s) the motion looks fine. At slow speeds (less than 1 m/s), the object stutters — you can see it pause briefly at curves and then catch up on straights. The framerate is steady; only the per-frame movement varies.

What Causes This

Knot-index parameterization. By default, Unity Splines parameterize by knot index. t = 0.5 sits halfway through the knot count, not halfway along the arc length. With non-uniform knot spacing, equal t deltas produce unequal arc deltas.

Per-frame t increment too small. At low speeds, you advance t by tiny amounts. Floating-point precision loses sub-knot positions, snapping the object to the nearest discrete sample.

Tight curves with low knot density. A 90-degree turn with only two knots on either side has heavy tangent inflation between them. Mid-curve, the spline curves sharply, but the parameterization still ticks linearly.

Update vs FixedUpdate timing. If you update position in FixedUpdate but render interpolation interpolates against an outdated parameter, the visual stutter is a sampling artifact.

The Fix

Step 1: Switch to distance-based traversal.

using UnityEngine;
using UnityEngine.Splines;

[RequireComponent(typeof(SplineContainer))]
public class SplineWalker : MonoBehaviour
{
    [SerializeField] private SplineContainer container;
    [SerializeField] private float speedMetersPerSec = 2f;

    private float distance;
    private float totalLength;

    void Start()
    {
        totalLength = SplineUtility.CalculateLength(container.Spline, container.transform.localToWorldMatrix);
    }

    void Update()
    {
        distance += speedMetersPerSec * Time.deltaTime;
        if (distance >= totalLength) distance -= totalLength;

        SplineUtility.GetPointAtLinearDistance(
            container.Spline, distance / totalLength, distance, out float tAtDistance);

        Vector3 pos = container.EvaluatePosition(tAtDistance);
        Vector3 fwd = (Vector3)container.EvaluateTangent(tAtDistance);
        transform.position = pos;
        if (fwd != Vector3.zero) transform.rotation = Quaternion.LookRotation(fwd);
    }
}

Distance parameterization keeps motion at exactly speedMetersPerSec regardless of knot density.

Step 2: Add knots through tight curves. In the Spline Editor, insert extra knots in sections that curve sharply. More knots means smoother per-distance evaluation.

Step 3: Smooth tangent modes. Select all knots, set their tangent mode to Auto Smooth or Mirrored. This eliminates abrupt direction changes at knot boundaries.

Step 4: Move in FixedUpdate for physics-tied followers. If the walker drives a Rigidbody, do the position update in FixedUpdate using the physics delta. Use Rigidbody.MovePosition rather than direct transform.position assignment so interpolation smooths intermediate frames.

void FixedUpdate()
{
    distance += speedMetersPerSec * Time.fixedDeltaTime;
    if (distance >= totalLength) distance -= totalLength;
    rb.MovePosition(GetPointAlongSpline(distance));
}

Step 5: Cache spline length once. CalculateLength is not free. Compute on Start and recompute only when the spline changes. Subscribe to SplineContainer.Spline.changed if you allow runtime edits.

Verifying Smoothness

Add a simple debug line that records the walker’s position every frame. After a slow lap, the trail should be evenly spaced. If you see clustering at curves, distance parameterization is not yet active or knot density is too low. If you see clustering at straights, your speed code is the issue.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Splines move you by t. Players see meters. The two are not the same. Walk by distance, not by parameter.”

Related Issues

For Cinemachine following splines, see Cinemachine Camera Jitter. For physics-based motion, see Physics Jittery Movement.

Distance parameterization. Smooth tangents. FixedUpdate for physics. The walker glides.