Most players lose more time to forgetting than to bad tuning. You find a setup that works, play something else for a week, come back, change one thing, and no longer know what the original was.
What a useful entry contains
- The car and its current upgrade state
- The race length the tune was built for
- Each setting you changed, with the value
- Your nitrous deployment cue
- A one-line note on how the run felt, not just the result
That last line matters more than it looks. "Spun on launch unless I feathered it" tells future-you what to fix; a bare time does not.
One row per change
Do not overwrite a row when you adjust something. Add a new one. The value of the log is the sequence, because it shows you which direction was working before you overshot.
Reverting is the point
A log lets you go back. Without it, every experiment is one-way, and players avoid experimenting because a bad change is permanent in practice.
Per-race-length entries
The same car can hold two or three legitimate tunes for different race lengths. Keep them as separate rows, clearly labelled, so you are not rebuilding a setup you already solved.
Keep it boring
A spreadsheet, a notes app, or the printable template in our resources section all work. The format matters far less than doing it the same way every time.
Related CSR2MODX reading: CSR2 tuning hub · Best cars · Car database
- tuning
- dyno
