Help & basics.

What should I tell the engineer?

Start with your car, track and the behaviour you want to understand. Say where it happens: while braking, turning in, holding a corner or accelerating out. Mention whether it starts straight away or builds during the stint.

You can ask a short question, report a result or correct something the engineer misunderstood. Use your own words.

Words you might hear

Understeer

The car turns less than you want and runs wider than your intended line.

Oversteer

The rear starts to slide outward and the car rotates more than you intended.

Corner entry

The approach and initial turn into a corner. Say whether you are still braking when the problem happens.

Mid-corner

The part of the corner where you are holding the turn, between the initial turn-in and the exit.

Corner exit

The part where you accelerate away and begin unwinding the steering.

Stint

A continuous run of laps. Some problems only appear after several laps, so say how far into the run you noticed them.

These descriptions help you explain a symptom. They do not identify its cause or prescribe a setup change.

How do I send files?

Open a conversation and use the paperclip beside the message box. Send one file per message: a .svm setup up to 1 MB, or a .duckdb telemetry file up to 25 MB.

Add a sentence about the run. A telemetry comparison needs the same car and track. The engineer uses whole-session summaries; an upload does not provide corner-by-corner alignment.

Every upload gets a reply. If the format is unsupported or the file cannot be read, the reply will explain that.

How should I test a change?

Test one adjustment at a time. Give yourself enough laps to check the behaviour that brought you here, then tell the engineer what improved, what stayed the same and whether anything became worse.

A partial improvement is useful evidence. Report it as a partial improvement, including any trade-off, rather than calling the whole problem solved.

How long does a conversation stay open?

A chat closes after four hours of inactivity, or 48 hours from its first usable engineer reply, whichever comes first. Sending an accepted message or upload, or receiving a saved reply, counts as activity. Keeping a tab open does not.

There is no per-conversation message ceiling. A chat can also end when you or the engineer close it. Closure is permanent: its messages and uploads are deleted from the live app and cannot be reopened.

Download any notes you want to keep from your account while the conversation is still open. Minimal usage records remain for cost accounting; backups and provider retention are separate from live chat deletion.