TL;DR
Sim racing is a lane on OpsUpdate. The angle is operator-shaped: telemetry as observability, setup as configuration management, FFB tuning as parameter optimisation. The same instinct you use to read p99 latency on a dashboard transfers cleanly to reading a brake-pressure trace on a slow corner.
This post is a short list of pro tips that work regardless of which platform you race or which wheel base sits on your desk, plus the running order of posts queued for the lane.
Eight pro tips that actually move lap times
These are hardware-agnostic. They apply on iRacing, ACC, LMU, AMS2, and rFactor 2 alike. None of them require gear you don't already have.
1. Don't upgrade the loudest component - upgrade the next thing stopping you from learning
Most upgrade decisions get framed as "what's the best wheel for $X?" That's the wrong question. The right question is: what is currently the bottleneck on what I can learn from a session? Sometimes that's the wheel. Sometimes it's the brake pedal. Sometimes it's seat position. Sometimes it's a 60Hz monitor when you're trying to read kerb behaviour. Solve the named bottleneck, not the loudest one.
2. Reference-lap discipline beats raw lap time
"Fastest lap of the day" is a worse reference than "best of your last ten consecutive laps." A single fastest lap can be a lucky combination of a slipstream, a clean track, and tyre temps that you'll never repeat. Comparing your current lap to a stable median teaches you more than chasing a one-off.
A stronger habit: keep a running median of your last 5–10 clean laps and compare against that. Half the regressions you'll see in a session are statistical noise.
3. Read the four channels together, not one at a time
Brake pressure, throttle, steering input, and speed. You can read each one alone and learn very little. Read all four together - overlaid on the same time axis - and the corner is no longer abstract. Where the brake comes off, where the steering goes in, where the throttle starts to roll on, and how the speed responds to all three - that's a whole story per corner.
A whole post is queued on this. The summary: don't analyse single channels.
4. Calibrate pedals on a cadence, not when something feels off
Load-cell brakes drift. Springs and rubber stops settle in. Pedal force at lap 1 is not pedal force at lap 200. If you race seriously, recalibrate every couple of weeks regardless of how things feel - by the time something feels wrong, you've already been compensating with technique for sessions, and the technique is now wrong.
5. Eyes-on-road, not eyes-on-dash
Move critical information to needles, lights, or coloured blocks - never numbers you have to read. Peripheral vision picks up a needle moving long before it picks up a digit changing. Tyre temps as four colour blocks beats four numbers. Fuel as a horizontal bar beats "12.4 L". Lap delta as a single number, big, in the line of sight is the one exception worth making.
6. Wired network, every time
Online racing has a tighter latency budget than people think. Jitter is the killer, not raw bandwidth. A solid 5 Mbps wired connection beats a 100 Mbps Wi-Fi connection every time, because Wi-Fi jitter under household load is unbounded. If you can't run an Ethernet cable, at minimum put your sim PC on its own 5GHz SSID, isolated from every other device on the network.
7. Practise corners, not laps
The fastest way to improve at a corner is isolated repetitions of that corner, not running another full race. Most sims have a "test session" or "practice from this corner" mode. Use it. Twenty minutes on Eau Rouge or the Bus Stop in isolation will teach you more than five full laps of Spa.
The mental shift: deliberate practice, not volume.
8. Tune FFB force down until you can read it
A wheel that fights you all the time saturates the channel that tells you what the front tyres are doing. The default force settings on most direct-drive bases are too high for the kind of multi-hour session that actually teaches you something. Dial the overall force down until your hands and forearms can sustain a 60-minute stint without tensing up. The signal you lose by dropping force is less than the signal you lose to tense, fatigued forearms.
The same applies to dampening - too high and the wheel feels like it's running through molasses; you stop trusting it; the channel goes silent.
What's coming on the lane
A rough running order, subject to drift. Each post will be hardware-agnostic where it can be, and explicit about its assumptions where it can't.
1. Telemetry reading 01 - the four channels
The expanded version of pro tip #3. What each of brake / throttle / steering / speed actually tells you, what the lies are, what shape a "good" trail-brake looks like vs an "I trail-braked too hard and the rear stepped out" trace. Worked example with anonymised lap data.
2. The setup notebook
A template I actually use, in MDX, with one row per session and the discipline that makes setups not regress under change. Includes the spreadsheet layout for "what changed", "what felt different", "what the lap-time delta said". The bridge from intuition to evidence.
3. MoTeC i2 Pro for iRacing exports
Exporting iRacing telemetry into MoTeC i2 Pro and getting a layout that's actually useful in 60 seconds. The channels that don't survive the export cleanly. A starting workspace you can copy.
4. Rig hygiene - calibration cadence and pedal maintenance
What to check weekly, what to check monthly, what to check before a serious race. FFB sanity routine. Pedal cleaning (you wouldn't believe what gets in there). Button-box rebind etiquette so the layout you wrote down on paper still matches reality.
5. A car-and-track notebook - one car, one track, one fortnight
Working example of pro tips #2, #3, and #7 applied. One car (probably the Porsche 992 GT3 R or the Ferrari 296 GT3), one track (probably Mount Panorama because operator-friendly Australian time zone), every change documented over two weeks, every lap-time delta honest. The output is the post; the exhibit is the spreadsheet.
Likely to follow
- Cognitive-load notes from long stints - what to spend attention on at lap 1 vs lap 50
- The case for and against motion (and what an entry-level haptic stack should and shouldn't try to be)
- Network diagnostics for sim racing - packet loss vs jitter, the right order to investigate, when to actually call your ISP
- A short pass on FFB tuning that's about signal not force
If a specific question would be useful to answer earlier, the About page has contact details and the RSS feed carries every new post.
Coda
The lane exists because the discipline rewards method. Setups are config. Telemetry is observability. Practice is deliberate iteration with feedback. Everything you already know how to do at work transfers - you just have to be willing to read the data instead of trusting your hands.
More to come. The first telemetry-reading post lands next.