Where do I lose time on the brakes?
Overlay your brake trace with a leaderboard lap on the 2D or 3D map and see whether you brake too early or release too soon at the apex.
Get free AI analysis of every F1 lap: ask your own AI race engineer where you lose time, and it answers from your real telemetry. Switch on UDP telemetry in the game once, start the Flowix agent, and every lap in practice, qualifying, races and time trial is recorded with tyre and brake temperatures, ERS, DRS or active aero, dampers, weather and sector splits.
| Setting | Default | For Flowix |
|---|---|---|
| UDP Telemetry | Off | On |
| UDP Broadcast Mode | Off | Keep |
| UDP IP Address | 127.0.0.1 | Keep |
| UDP Port | 20777 | Keep |
| UDP Send Rate | 20 Hz | 60 Hz (optional) |
| UDP Format | Game year | Keep (2025 / 2026) |
| Your Telemetry | Restricted | Keep |
F1 pushes its data over the network instead of shared memory, so a few details differ from other sims.
The game sends to one port only. Add forwarding ports in the agent settings and Flowix passes every packet on, so SimHub, a dash or Crew Chief keep working. You can also change the port Flowix listens on.
Flowix records at the rate the game sends. The default 20 Hz works, but 60 Hz gives smooth brake and steering traces through quick direction changes.
A lap with a flashback is dropped because its trace was rewound. Laps the game invalidates, or with three wheels off track, are flagged and never count as a record.
Laps are stored under the team you drive for. With equal car performance on, every car is one F1 2025 or F1 2026 entry; F2 laps share one F2 car.
No laps showing up? Check that UDP Telemetry is On, Broadcast Mode is Off, the IP is 127.0.0.1, the port matches the agent settings and the UDP Format is 2025 or 2026; older formats are ignored. The game has to run on the same Windows PC as the agent, so console play is not supported.
Recorded on every packet the game sends, up to 60 times per second. The last row lists what the game keeps to itself.
| Area | Recorded data | Status |
|---|---|---|
| Car on track | Lap time and distance, speed, world position, velocity vector, pitch / yaw / roll | Recorded |
| Your inputs | Throttle, brake and clutch, steering, gear, engine RPM, front brake bias | Recorded |
| Tyres | Surface temperature and pressure of each tyre, wheel slip speed, fitted compound | Recorded |
| Brakes | Brake temperature at each wheel | Recorded |
| Chassis | Suspension travel and damper speed at all four corners, front and rear ride height | Recorded |
| Energy & aero | ERS store charge, DRS available / open, 2026 active aero straight mode, fuel remaining | Recorded |
| Car health | Wing and engine damage | Recorded |
| Conditions | Air and track temperature, rain intensity | Recorded |
| Not shared by the game | Inner / outer tyre zone temperatures, per-corner ride height, handbrake, clutch temperature and wear | Empty |
Overlay your brake trace with a leaderboard lap on the 2D or 3D map and see whether you brake too early or release too soon at the apex.
Follow the ERS store and top speed along the lap. A battery that runs flat before the last straight explains a slow final sector.
Front and rear ride height drops and damper spikes show where the floor hits the track, so you know whether to raise the car or take a different line over a kerb.
There’s about 0.34 s of free time. Your best sector 1 plus your best sectors 2 and 3 adds up to 1:19.582. Almost all of that sits in the opening corner.
Link Claude, ChatGPT, Gemini or a model running in LM Studio to Flowix, then ask something like “Where does the fastest Suzuka lap gain on me in sector 1?” The assistant pulls your actual F1 samples and answers with corner names, metres and km/h.
Sign up in seconds, install the lightweight agent, and watch your telemetry sync automatically as you lap the circuit.
We don't track you. No ads, no analytics, no tracking cookies. Privacy policy