Fix: Unreal Chaos Vehicle Tire Friction Too Low

A Chaos Vehicle skitters around like it’s on ice. The road is concrete with no rain effect. Even gentle steering produces oversteer; braking locks the wheels and slides for meters. The vehicle’s suspension and mass values are reasonable; the tires just don’t grip.

The Friction Stack

Chaos Vehicles compute per-wheel friction as a product:

EffectiveFriction = TireConfig.FrictionScale
                  * PhysicalMaterial.Friction
                  * SuspensionLoad / NominalLoad

If TireConfig.FrictionScale is 1.0 (default) and the road material’s Friction is 0.7 (default for a generic PhysicalMaterial), effective friction is 0.7 — far below the 1.5–3.0 range expected for an arcade racer.

Step 1: TireConfig Asset

Open your TireConfig Data Asset:

FrictionScale: 2.5   // up from default 1.0

This is the main lever. Higher = grippier tires regardless of surface.

Step 2: Road PhysicalMaterial

Open the road’s PhysicalMaterial (assigned via the road mesh’s material or directly on the collision):

Friction: 1.5
RestitutionCombineMode: Average

Different surface types should have different values: dry concrete 1.5, wet 0.8, ice 0.3, gravel 1.0 with high slip curve.

Step 3: Wheel Setup Slip Curves

Each wheel’s Lateral Slip Curve defines how much grip is available as the slip angle increases. Default curves are conservative. For drift-style cars, push the peak to ~0.7–0.8 friction at higher slip angles. For grip-focused cars, peak earlier with sharper rolloff.

Open BP_WheeledVehiclePawn → Wheels → expand a wheel entry → Slip Curves.

Step 4: Suspension and Mass

If the vehicle’s mass is wrong, tire load is wrong. A 1500 kg sedan with mass set to 100 will feel like an empty toy regardless of friction. Open VehicleMovement → Mass and set realistic values for the vehicle class.

Suspension Compression Damping ~2.0 and Suspension Spring Force scaled to vehicle weight feels right for most cars. Too soft and weight transfer during turns drops grip on the inside tires below threshold; too stiff and you bounce.

Step 5: Verifying with Logs

Enable debug HUD: chaos.Vehicle.ShowAll 1. Shows per-wheel slip, normal force, friction force in real time. Drive aggressively; check whether you’re saturating the slip curve. If slip stays at 100% the moment you turn, friction is too low; if it stays at 0% even during sharp turns, the cars are skating without modeling slip.

Verifying

Build a test track with three surfaces: dry concrete (Friction 1.5), wet asphalt (0.8), ice (0.3). The vehicle should grip well on dry, slip moderately on wet, and slide dramatically on ice. If all three feel similar, the slip curve or TireConfig is dominating — revisit.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unreal 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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Unreal. 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

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

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 Unreal-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

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

Within Unreal, 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

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

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.

“Chaos tire friction is a product of three numbers. Raise the wrong one and you barely feel it. Raise the right one and the car transforms.”

Build a benchmark drive cycle (straight + corner + brake) and time it whenever you tune friction — subjective feel is unreliable for fine tuning.