A wheel that pulls to one side is almost never a broken wheel. Nine times out of ten it’s a center-calibration offset or a stray force effect the software is feeding into the motor, and both are fixable in about two minutes once you know where to look. Before you start a return ticket or convince yourself the encoder is toast, do one thing: figure out whether the pull happens in every game and on the Windows desktop with no sim running, or only inside one title. That single question splits the entire problem in half.

So here’s the short answer you came for. If it pulls everywhere, including with the sim closed, it’s a hardware-level center or a constant force baked into your base’s tuning menu, and you recalibrate. If it pulls only in one game, that game has a steering offset, a linearity setting, or an auto-center spring turned up, and the base is fine. Real mechanical faults, the kind that mean a repair, are far down the list and usually announced by grinding or a dead spot, not a gentle lean. Let’s go through the causes in the order you should actually check them, most common first.

Step zero: the two-minute triage

Kill the sim. Open Windows and search “Set up USB game controllers,” pick your base, hit Properties, and watch the X axis (steering) crosshair while you let go of the wheel. Direct drive bases will spring back to somewhere; note where. Then physically hold the rim dead straight by eye and read the percentage. Center should sit at 50%. If it reads 47% or 53% resting straight, there’s your pull. The firmware thinks straight-ahead is somewhere it isn’t, so it’s constantly nudging you back to its wrong idea of center.

Now the other half of triage. Turn force feedback strength to zero in the base software (Fanatec Control Panel, Moza Pit House, Simucube True Drive, Simagic SimPro Manager, whichever you run). If the pull vanishes with FFB off, it’s a force, meaning something is commanding the motor. If the wheel still physically wants to rotate toward one side with the motor dead, that’s mechanical or a stuck axis, and that’s the rare one. Do these two checks before anything else. They save you an hour of poking at in-game sliders that were never the problem.

Cause 1: your center is miscalibrated

This is the big one. Direct drive bases set their electrical center on power-up or via a calibration button, and it drifts. Fanatec CSL DD and the Fanatec GT DD Pro want you to hold the wheel straight and long-press the tuning button (or use “calibrate” in the Control Panel) so it relearns center. Moza bases have a wheel-center calibration in Pit House that takes two clicks. Simucube stores center in True Drive. If you swapped a rim, remounted a quick release, or the base lost power mid-session, center can end up a few degrees off, and a few degrees is exactly what a pull feels like.

The tell: the wheel sits happily at a small angle and fights you when you straighten it, but a fresh calibration makes it disappear completely. If recalibrating fixes it for one session and it comes back next boot, the quick release is the suspect, not the firmware. A worn or slightly loose QR (looking at you, older Fanatec QR1 plastic hubs) lets the rim seat a hair off each time you clip it on. Snug it, or upgrade the hub.

Cause 2: a constant force hiding in the tuning menu

Every base has a stack of global effects, and two of them will pull you sideways if they’re misconfigured. The first is an auto-center spring (sometimes labeled SPR or “center spring”). On a proper direct drive base this should be off or near zero, because the game generates its own centering through the physics. If it’s turned up and your center is slightly off, the spring yanks you toward the wrong center all the time. The second is a stuck constant-force offset, which can happen after a firmware update leaves a value cached. A full base restart, or resetting the tuning set to default and rebuilding it, clears these.

Damper (DPR) and friction (FRI) don’t cause a directional pull on their own, so don’t chase those. If you’ve been raising every slider hunting for “weight,” turn them all back to sane defaults first. A clean base tune is DRI/damper low, SPR off, and let the game do the work. People on the Moza and Fanatec Discords burn evenings on this because the tuning menus expose fifteen parameters and the manual explains three of them.

Cause 3: the game itself has a steering offset

If triage told you the pull only happens in one sim, stop touching the base. iRacing auto-maps wheel range and rarely offsets center, but a botched wheelcheck or a hand-edited controls.cfg can put a bias in. ACC and rF2 both expose steering linearity and a center deadzone, and a non-zero offset there reads as a pull. Assetto Corsa (the original) is notorious for picking up a Windows calibration offset. Automobilista 2 and Le Mans Ultimate use rF2-family settings, so same story.

The fix is per-game: delete the controller profile in that title and recreate it, recalibrating steering when it asks you to turn full lock each way. Nine times out of ten a game-only pull is a saved profile that captured a bad center on the day you set it up. Gran Turismo 7 on console deserves its own note: it has almost no user-facing FFB tuning, so a pull there is nearly always the base’s own center or, on a Fanatec GT DD Pro, the compatibility mode not matching what GT7 expects.

Cause 4: Windows calibrated your axis for you

Windows will sometimes apply its own calibration curve to a controller, and it loves to add a center offset you never asked for. In “Set up USB game controllers,” open Properties, go to Settings, and hit “Reset to default.” If there’s a “Calibrate” wizard, either run it carefully to full lock both ways or reset and leave it alone so the base’s own center is what the game reads. This one is sneaky because it survives reboots and affects every game at once, so it can masquerade as a hardware fault. Rule it out early. Pedals throwing their own calibration errors? That’s our sim pedals not calibrating guide.

Cause 5: desk flex and a crooked mount

Here’s a physical cause people miss. Direct drive puts real torque through the clamp, and if your wheel is clamped to a desk, the desk flexes. A base mounted slightly twisted, or a clamp that lets the whole unit rock a few degrees under load, changes where “straight” feels like relative to your body even when the electronics are perfect. You end up holding a tiny correction constantly and reading it as a pull.

This is worse the more torque you run. A 5 Nm base on a desk is usually fine. Anything from 8 Nm up, and a flexing desk turns every hard corner into a wrestling match, with the rim seeming to settle off-center because the mount deflects and returns. If you’re serious about direct drive, a rigid mount fixes more problems than any tuning slider. A wheel stand or an aluminum-profile cockpit like the Sim-Lab or GT Omega frames removes the flex entirely, and it’s the single upgrade that makes a mid-torque base feel like it costs twice as much. If you’re on a desk, at least move the clamp to the thickest, most supported part of the desktop and check the base sits square.

Cause 6: belt wear, if you’re on an older belt-driven wheel

Belt wheels are a different animal. A Thrustmaster T300, T-GT, or a Logitech gear-driven G29 can develop a genuine mechanical pull as the belt stretches unevenly or a gear wears, and no amount of software calibration fully hides it. If you own one of these and the pull grew over years of use, and it persists with FFB off, that’s mechanical wear. It’s not usually worth repairing a five-year-old belt base. This is the point where I’d stop patching and put the repair money toward a used direct drive base instead, because the belt-wheel plateau is real and you’ll feel the difference in a week.

Direct drive bases don’t wear this way. There’s no belt, no gear lash, so a DD base that suddenly pulls is a settings or calibration issue, not fatigue. That reliability is a big part of why the Moza R5, R9, and the Fanatec CSL DD are the default recommendations now instead of the old belt wheels.

Cause 7: the car is supposed to pull

Don’t laugh, this catches people. Some pulls are the sim doing its job. A track with banking (Daytona, the Nordschleife’s Karussell, high-banked ovals) loads the wheel toward the low side, exactly like real life. Aggressive toe or a broken suspension in the car setup will tug you. Damage after contact pulls hard toward the bent corner. If the pull only shows up in one car, on one track, or after you clipped a wall, the physics engine is telling you something true and there is nothing to fix. Load a different car on a flat track like a road-course pit straight and see if it’s gone.

Cause 8: the actual hardware fault

Last, because it’s least likely: a failing encoder or a Hall sensor can report a false position and drive the motor to a wrong center that recalibration won’t hold. The signs are a pull that returns instantly after every calibration, sometimes with jitter or a notchy feel near center, and it happens across all games and the desktop. A shake or buzz at center without the pull is usually oscillation instead, which our direct drive wheel rattle at center guide covers. If you’ve cleanly ruled out center calibration, tuning-menu forces, Windows, and the mount, and it still won’t hold center, that’s a support ticket. On Fanatec that means bracing for their support queue, which has a deserved reputation for being slow. Moza’s warranty handling has been better in my experience, partly because they’re newer and hungrier, though their support footprint is thinner outside major regions.

FAQ

Why does my wheel pull left after a firmware update? Updates sometimes reset or cache a bad center and occasionally re-enable an auto-center spring in the default tune. Recalibrate center, then check SPR is off in your base software. This is common enough on Fanatec and Moza that it’s worth doing as routine after any firmware bump.

My wheel is centered in Windows but still pulls in iRacing. Now what? That’s a game-side profile. In iRacing, remove the wheel from your controller config and re-add it, letting it recalibrate lock-to-lock, or re-run the wheelcheck process for your FFB. A center that’s correct in Windows but wrong in one sim is always that sim’s saved calibration, not the hardware.

Can desk flex really cause a pull, or is that overblown? It’s real above roughly 8 Nm. The base twists under load and returns slightly off, so you hold a constant micro-correction. Clamp to the sturdiest part of the desk to test it, and if the pull eases, a rigid stand or cockpit will kill it for good.

Before you spend a cent

Recalibrate center and check for an auto-center spring first. That fixes the clear majority of these, costs nothing, and takes two minutes. If the pull only lives in one game, rebuild that game’s controller profile and leave the base alone. Only reach for the wallet in two situations: you’re on an aging belt wheel where the pull is mechanical and growing, in which case a used direct drive base is a better use of money than a repair, or your direct drive base is on a flexing desk running real torque, in which case a rigid mount or cockpit frame is the fix. If you’ve done all of that and it still snaps back off-center after every calibration with jitter near the middle, then and only then is it a warranty claim. Check the cheap causes before you assume the expensive one.