Racing Wheel Calibration PC / Pedal Deadzone Settings

A badly calibrated wheel feels vague, pulls to one side, or registers brake input while your foot is resting. A well-calibrated one disappears, and you stop thinking about the hardware entirely.

The confusing part is that "calibration" happens at three separate levels: the wheel's own firmware, your PC, and each game. Settings at one level can quietly override or compound with another, which is why people end up with a wheel that feels wrong despite having adjusted everything they could find.

Here's how to work through all three properly, and how to set deadzones without destroying the feel you paid for.

The golden rule: start at zero

Before any specifics, internalise this, because it's the opposite of how most people approach it.

Dead zones should be as low as your hardware allows, ideally zero. On healthy equipment, every calibration setting should start at zero and only be raised when a specific problem demands it. Deadzone, linearity, and saturation exist to compensate for hardware limitations, not to be tuned for their own sake.

A steering deadzone makes your car feel vague and harder to catch in a slide. A brake deadzone throws away the initial pedal travel where trail-braking precision lives. Every point you add costs you something real, so add the minimum that solves an actual problem and stop.

Step 1: Calibrate at the wheel level first

Start with the manufacturer's software, because settings applied here carry across every game.

Install the right software for your hardware: G HUB for Logitech, the Thrustmaster control panel for Thrustmaster, and Fanatec Wheel Properties or Fanalab for Fanatec. Higher-end and pedal-specific hardware often has its own utility too.

Two things to do here.

Centre calibration. If your wheel doesn't sit true at centre, everything downstream inherits that error. Most Logitech and Thrustmaster wheels recalibrate themselves when unplugged and plugged back in, which is worth trying first. Higher-end wheels usually need manual centre calibration, and Fanatec exposes this through Wheel Properties under Settings, where a guided Wheel Centre Calibration walks you through it.

Rotation degrees. Set your maximum wheel rotation in the software, then match it in-game. Mismatched values are a common cause of steering that feels wrong in a way people struggle to describe. For open-wheel racing, 360 degrees is a common target that gives one-to-one steering; GT and road cars typically want more, often 540 to 900.

Also update your wheel's firmware while you're here, since firmware affects both feel and calibration behaviour.

Step 2: Verify at the Windows level

Windows has its own view of your wheel, and it's the fastest place to confirm the hardware reads correctly before you blame a game.

Press Windows + R, type joy.cpl, and press Enter to open the Game Controllers panel. Select your wheel and open Properties, where you'll see live axis readouts for the wheel and each pedal.

Now the important test. Take your hands off the wheel and your feet off the pedals completely, then watch the values. A healthy setup reads zero, or extremely close to it, on every axis. Then turn the wheel fully in each direction and press each pedal fully, confirming each reaches its maximum.

This is your ground truth. If the wheel reads off-centre here, fix it at the hardware level rather than compensating in-game. If a pedal reads non-zero while untouched, that's what a deadzone is for, and now you know exactly how much you need.

Windows also has a calibration wizard for some devices under the same panel, and the critical rule matches controller calibration: don't touch the wheel or pedals during the centring step, since resting your hands there teaches the system a wrong centre. Our guide on calibrating a controller on Windows 11 covers reaching and resetting that wizard, and the same principles apply to wheels.

Step 3: Understand the three in-game settings

Most racing games expose the same three settings per axis, and they're widely misunderstood.

Deadzone sets the minimum input required before the game registers anything. Raising it means you must turn or press further before anything happens. Use it to eliminate phantom input, not to change feel.

Saturation is essentially the reverse: it determines how much input is needed to reach 100%. Raising saturation means you reach full lock or full brake with less physical travel. This is genuinely useful with stiff brake pedals where you struggle to hit 100% input.

Linearity changes the shape of the input curve between those two points. Adjusting it gives you finer, more granular control at the start of the travel, with faster response toward the end. Many sim racers increase pedal linearity specifically to gain more precision in the early part of the brake travel.

A useful way to think about them: deadzone sets where input starts, saturation sets where it ends, and linearity sets what happens in between.

Step 4: Set your deadzones by measurement

Here's the method that beats guessing.

Go to the game's calibration or controls screen where input bars are displayed. Relax completely: hands off the wheel, feet off the pedals, sitting normally. Watch the bars for ten seconds.

Set each deadzone one increment above whatever flicker you see, and no higher. If the bars sit perfectly still at zero, leave the deadzone at zero. That's the whole method, and it produces a better result than any recommended value someone else publishes, because it's calibrated to your specific hardware's noise floor.

Some practical starting points from that approach:

Steering. Zero on a healthy direct drive or belt wheel. Gear-driven wheels like the Logitech G29 often benefit from around 1% to stop the gears jittering left and right on straights. Avoid going beyond roughly 5%, since the car becomes vague and harder to correct.

Brake. This is where deadzones most often earn their place. If the game registers brake input while your foot merely rests on the pedal, raise the brake deadzone into the 1% to 5% range until it goes quiet. A dragging brake costs time on every straight without you feeling it, which makes this one of the most valuable corrections available.

Throttle. Usually zero to 2%, again set just above any resting flicker.

The same logic that governs controller deadzones applies here, and our deadzone test demonstrates the principle of measuring your resting noise before setting a value.

Pedal type changes what you need

Worth knowing, because it explains why advice varies so much between people.

Potentiometer pedals, found on the Logitech G29 and G920 and much of the Thrustmaster range, measure pedal position. They're perfectly usable, but they wear over time, and a worn potentiometer produces exactly the resting flicker that forces you into larger deadzones. If your brake deadzone requirement has grown over the years, that's why.

Load cell pedals measure the force you apply rather than how far the pedal has moved, which is closer to how real brakes work and lets you brake by pressure rather than by travel. They typically need smaller deadzones because they're less prone to noise, and they report at higher frequency. If you're using one and still needing a large brake deadzone, it may need re-zeroing in its software.

The practical implication: don't copy someone else's deadzone values if they're using different pedal hardware from you.

Common problems and their fixes

The car pulls to one side on straights. Your wheel centre is off. Fix it with centre calibration at the hardware level rather than adding steering deadzone, which masks the symptom while making steering vague.

Brake registers while your foot rests on the pedal. Raise brake deadzone by 1% to 5%, or re-zero a load cell if supported.

You can't reach 100% brake. Increase brake saturation so full input arrives with less travel. Stiff pedals on some wheels make this common.

Steering feels vague or disconnected. Your deadzone is probably too high. Reduce it toward zero and solve any centring problem at the hardware level instead.

Settings don't seem to apply. Check you're editing the active preset and saving it, since some games cache inputs until you reload the session or return to the garage.

Steering feels wrong in a way you can't name. Check rotation degrees match between your wheel software and the game. This mismatch is responsible for a surprising share of unexplained complaints.

Don't fix force feedback with calibration

One trap worth naming explicitly. If the wheel feels notchy, dead in the centre, or vague, the instinct is to reach for deadzone and linearity. But those are input-shaping settings, and force feedback is a separate system entirely.

Solve force feedback problems in the force feedback settings, and calibration problems in the calibration settings. Mixing them produces a setup where neither is right and you can't work out why. Our hardware calibration guide covers where the boundary sits between what calibration can correct and what it can't.

The short version

Calibration happens at three levels, so work through them in order: manufacturer software first for centre calibration, rotation degrees, and firmware; then Windows via joy.cpl to confirm the hardware reads zero at rest and reaches full travel; then per-game settings. Start every deadzone at zero and raise it only to silence actual measured flicker, one increment above whatever you see with your hands and feet off. Use saturation when you can't reach 100% input, and linearity to shape the curve between. Fix a pulling car with centre calibration rather than deadzone, and keep force feedback tuning entirely separate from calibration.