A car that pushes on entry, holds fine at the apex, then gets loose on exit isn’t broken or unpredictable, it’s just responding to the fact that weight transfer is different in each phase of the corner. The fix is to stop diagnosing “the corner” as one thing and start diagnosing entry, apex, and exit as three separate problems.
Why the phases behave differently
Every corner has three distinct phases, each with different physical demands on the car:
- Entry: braking shifts weight forward, loading the front tires while the rear loses load.
- Apex: braking and throttle are minimal, weight is loaded laterally onto the outside tires in a steady arc.
- Exit: throttle shifts weight rearward, loading the rear tires while the front loses load.
Because the load on each tire changes completely between phases, a setup change that helps one phase can do nothing, or actively hurt, another. That’s not a flaw in your setup process, it’s the nature of the corner.
How to work through it
- Identify which phase has the problem. Isolate exactly when in the corner the car misbehaves: under braking, at steady-state, or under throttle.
- Identify the imbalance in that phase. Is the front giving up first (understeer) or the rear (oversteer)?
- Apply the fix specific to that phase. Entry, apex, and exit each respond to different tools, springs for entry and exit transitions, anti-roll bars and camber for apex balance.
- Move to the next phase only after confirming the first is fixed. Don’t try to solve all three phases with one change.
See the phase-specific guides: entry understeer, entry oversteer, apex understeer, apex oversteer, exit understeer, and exit oversteer.
The bigger picture
Once you can name the phase and the imbalance, “the car behaves differently everywhere” turns into a short list of specific, solvable problems. This is the foundation of all effective setup work.
This is the same phase-and-balance framework we built into onRails: identify the corner phase, identify the grip imbalance, apply the smallest effective change. If you’re diagnosing this by feel across a dozen setup sheets, onRails does that process for you.
Related questions
Is it normal for a car to need different balance in each phase?
Yes. Even a well-sorted setup usually carries a slightly different front-to-rear balance preference at entry, apex, and exit, because the physical demands genuinely differ.
Should I aim for identical balance everywhere?
No, aim for each phase to be predictable and controllable at the limit, not for the numbers to be identical across entry, apex, and exit.
What if I can’t tell which phase the problem is in?
Slow down and isolate it deliberately: brake and turn in without touching the throttle to test entry in isolation, then hold a steady speed through the apex, then focus only on the throttle application on exit.