PaceDynamics

One connected vehicle model

Build the car.
Understand the lap.

PaceDynamics connects suspension geometry, tyre models, aero maps, motors and batteries to whole-vehicle behaviour and lap time—so you can trace every setup decision from the component that changed to the seconds it gained.

Account access is currently by invitation only. Tell me you’re interested.

Templates / solved on open
Measured answers

01 / Templates

The app’s own library

Start from what you work on.

Every template the app opens with, in the areas its New project shows. Each opens on the tool it is about, with its answer or its lap already solved, ready to change into your own car.

I work on

    03 / How it works

    The simulation chain

    Five models between a part and a lap time.

    A lap time is not one calculation. The grip envelope says what the car can do, the racing line where it drives, the quasi-steady lap how fast it goes, the transient car whether it can be driven that way, and the optimal planner what it could do driven perfectly. Each answers its own question and says what it leaves out.

    Solid arrows are inputs; the dashed one is a comparison. Pick a model to see how it is solved.

    01 / Grip envelope · GGV

    What can the car do at each speed?

    Under a second · in your browser

    The envelope is the edge of what the tyres, the aero and the drive allow together: at each speed, the most the car can accelerate or brake while it corners at a given lateral acceleration. Every quasi-steady lap, sweep and study reads it.

    The template's envelope at , and every point of its lap on : nearly every one sits on the edge of the envelope at its own speed.
    Cornering and braking grow with downforce. Drive does not: the motors limit acceleration at every speed, short of what the tyres could transmit, and from km/h the pack's power does.

    How it is solved

    1. The lateral limit. At a ladder of speeds, the four-wheel model sweeps the steer from straight ahead, trims the body slip until the yaw moments balance, and follows that branch to its peak lateral acceleration.
    2. Load transfer. Cornering moves load across the car through the roll centres, springs and bars; braking and drive move it between the axles. Each tyre's grip is read at its own load. That is how anti-roll bars, the roll split and brake balance reach the lap time.
    3. The combined edge. Below the lateral limit each tyre keeps its cornering share and offers the rest of its combined-slip grip to drive and braking. Motor torque, pack power and brake balance cap what is used; drag and rolling resistance come off the top.
    4. Downforce. Aero load grows with the square of speed, so the envelope widens as the car goes faster: g of cornering at km/h, g at .

    Use it for

    • Seeing what limits the car at a speed: grip, motor torque or pack power.
    • Judging a setup change — bars, balance, aero, tyres — before running a lap.
    • The input to every quasi-steady lap, sweep and design study.

    It leaves out

    • Time. Every point is a settled steady state: no turn-in, no yaw inertia, no body motion.
    • A yaw balance under drive and braking: each tyre keeps the cornering share of the steady corner, so the combined edge is an approximation.

    Which model answers which question

    The questionEnvelopeRacing lineQuasi-steadyTransientOptimal
    What limits the car at this speed: grip, torque or power?●○
    Which way through this corridor?○●
    How much lap time does this part or setup buy?●○○
    Points and energy over a Formula Student event?●
    Does the car turn in, overshoot, settle?●
    Can this lap actually be driven?●○
    What is the best this car could do?●
    One run on FSG, on a laptop~0.5 s~15 ms~15 ms a lap~30 sMinutes · on our server

    ● answers it○ in part, or slowly

    04 / One workflow

    Trace the consequence

    From a part to a decision—without rebuilding the car.

    A shared vehicle model keeps inputs, physics, studies and results connected. Change one assumption and every dependent answer knows.

    01

    Build

    Define the ingredients

    Geometry, tyres, aero, motors, batteries, mass properties and the track live as inspectable models with units and provenance.

    02

    Understand

    Solve the whole vehicle

    Follow kinematics, loads, ride, roll, yaw, forces, power and energy through the same car instead of a chain of disconnected sheets.

    03

    Explore

    Ask better what-ifs

    Compare variants, sweep sensitivities and optimise against goals and constraints while keeping the active design in view.

    04

    Decide

    Measure it on track

    See the lap, energy and event-score consequence, find where the gap lives and turn that stretch into the next study.

    05 / Agent interface

    PaceDynamics MCP server

    The same simulator has an interface for your assistant.

    Open a project, inspect or change a car, run the events, sweep a parameter, search the design space and export the result through natural language. The MCP server calls the same vehicle model and solver core as the app—so it does not invent a second version of the maths.

    Clauderemote or local Codexdesktop, CLI or IDE ChatGPTcustom MCP app

    ChatGPT custom apps require an eligible plan and workspace developer mode.

    PACE DYNAMICS / MCPREAL SERVER TOOLS
    1. 01project_open

      Load the same .pace.json project the browser uses.

    2. 02vehicle_get · vehicle_set

      Inspect the active model, change a setup and keep superseded inputs explicit.

    3. 03run_session · run_trace

      Run the scored field and read the solved path without a second calculation.

    4. 04sweep · study_run

      Explore sensitivity or search a constrained design on a cancellable worker.

    5. 05project_export

      Bring the updated project and filed results back to the app.

    Same solver coreOAuth-authorisedMetered computeEphemeral workspace

    06 / Suspension lab

    A real 3-D model, not a cutaway illustration

    From road-car struts to decoupled modes.

    Start from a solvable architecture, move every hardpoint and inspect the actual linkage in three dimensions. The template accelerates the first step; it never decides the design.

    Live kinematics model
    3D / FRONT AXLE

    Drag to orbit

    FORMULA STUDENT / PUSHRODPushrod suspension

    A rod from the lower wishbone pushes a rocker on the chassis shoulder. A 225 mm damper runs along the top at 1:1.

    07 / Built to inspect

    Simulation should show its work.

    01

    Connected by construction

    Suspension, tyres, aero, powertrain, energy, dynamics and lap time read from one version of the car.

    02

    Data stays distinguishable

    Measured, imported, assumed and derived values remain visibly different, with validity and simplifications called out.

    03

    Questions become studies

    Move from a lap-time gap to comparisons, sweeps and constrained optimisation without reconstructing the model.

    04

    Your browser does real work

    Most analysis runs locally, with server compute reserved for the genuinely harder solve.

    Private preview · by invitation

    Interested? Tell me where to send an invitation.

    PaceDynamics is currently available by invitation only. Leave your email and a short, pre-addressed message will open in your email app.

    Prefer to write directly? hello@pacedyn.dev