Car Mechanic Simulator's OBD Scanner Versus a Real One

Last winter a reader emailed me a photo of a box of parts on his garage floor: a new oxygen sensor, a new mass airflow sensor, a set of spark plugs and a fuel filter. Total spend was a little over £260. His engine management light was still on. The code was P0171, system too lean on bank 1, and he had been replacing parts in the order a forum thread suggested. When I asked how he had learned to diagnose, he said, a bit sheepishly, that he had put about 300 hours into Car Mechanic Simulator 2021.

I like that game. I have recommended it to people who want to learn what sits under a bonnet and where it goes. But its scanner teaches a habit that costs real money once you plug a real code reader into a real car, and I have now heard versions of this story from enough readers that it is worth laying out exactly where the game and the workshop part ways.

What the game's scanner does

In Car Mechanic Simulator 2021, diagnosis is a set of tools you pick from a menu. The OBD scanner checks the car's electronics. The compression tester checks each cylinder. A test drive path and a test track let you feel suspension and brake problems. And the examine mode lets you look at any part and see its condition as a percentage, often colour coded from green to red.

The design goal is clear: give the player a fair puzzle that resolves into a list of parts to buy and fit. When the scanner flags something, it points you toward a component, and once that component is replaced the job is done. That loop is satisfying, and for a game it is the right call. Nobody wants to spend forty minutes of play staring at fuel trim numbers.

The problem is that it trains a specific belief. A code equals a broken part. Replace the part, clear the code, finished.

What a real code actually tells you

A real diagnostic trouble code describes something the engine control unit noticed, not something it confirmed is broken. P0171 means the ECU has been adding more fuel than it expects to, for long enough that it decided to flag it. It does not know why. The O2 sensor that reports the lean condition is usually the messenger, not the culprit.

On the cars I see most often, the common causes of P0171, roughly in the order I check them, are a vacuum leak (a split intake hose or a perished PCV pipe), a dirty mass airflow sensor reading low, a weak fuel pump or blocked filter, and only then a faulty sensor. The reader with the box of parts had a cracked rubber elbow between the airflow sensor and the throttle body. It cost £14. Every part he had bought was fine.

The same pattern runs through most codes. P0300, random misfire, can be plugs, coils, injectors, a vacuum leak or low compression. P0420, catalyst efficiency below threshold, is sometimes a dead catalytic converter and sometimes a rear O2 sensor that is tired or an exhaust leak in front of it. Our guide on telling a real problem from a sensor glitch goes into that distinction in more depth.

Side by side

The live data row is the one I wish the game modelled. On a real car, the single most useful thing a cheap reader can show you for a lean code is long term fuel trim. If it reads +18 percent at idle and drops toward +4 percent at 2,500 rpm, that strongly suggests an unmetered air leak, because the leak matters less as total airflow rises. If the trim stays high at all engine speeds, you look harder at fuel delivery or the airflow sensor. That one comparison would have saved my reader £246.

The advice I would push back on

A common line in online forums is "just get the code read and replace what it says." It is popular because it is sometimes right, and because it feels like a plan. Some parts shops will even read your code for free and sell you the part listed on the printout.

I would rephrase it as "get the code read, then find out what makes that code appear." Search the code together with your make and model, not on its own, because model-specific patterns are real. A particular engine may have a known weakness in a breather hose or an intake gasket that produces the same code across thousands of cars. Then look at freeze frame data, which most readers store with each code, to see the engine speed, load and temperature when the fault was logged. A misfire that only ever appears with a cold engine at idle points somewhere very different from one that happens at motorway speed.

The game cannot teach this because it does not need to. Its faults are designed. Real faults are not.

Where the game still earns its keep

I do not want to be unfair. Car Mechanic Simulator is genuinely good at teaching layout: where the airflow sensor sits relative to the throttle body, what order things come off to reach a water pump, what a ball joint looks like. That spatial knowledge makes the first real job far less intimidating. Its compression tester also gets the principle right, and players who understand why a low reading on one cylinder matters have a head start. If a misfire has you stuck, our walkthrough on diagnosing a misfire without a scanner builds on exactly that kind of thinking.

Just treat the scanner screen in the game as a convenience the developers added for fun, not a model of how fault codes behave. More of our thinking on car games is in the games section.

One thing to do this week

If you own a code reader, plug it in with the engine warm and idling, find the live data screen, and write down short and long term fuel trims for both banks. Then hold the engine at about 2,500 rpm and write them down again. Keep those numbers somewhere safe. The day a lean or rich code appears, you will have a healthy baseline to compare against, which is worth more than any part on a shelf. If you have never used a reader before, start with how to read OBD2 codes at home.