Nine times out of ten, force feedback that dies partway through a race is one of three things: the wheelbase hit its thermal limit and quietly throttled, the USB connection dropped for half a second and the game never re-handshook, or a sim-side setting (usually a per-car FFB multiplier or a “reduce force when parked” rule) kicked in and you didn’t know it existed. None of those are hardware failures. Your wheel is probably fine.

The tenth time it’s a power supply, a loose emergency-stop, or a cable you crushed under the rig leg. That’s the order I’d check in, and I’ll walk through each one with what it actually looks like in practice, because the symptoms overlap enough that people replace a perfectly good base after a bad night of guessing.

First, figure out which “weak” you’ve got

There are really three different complaints hiding under “FFB stopped working,” and they point at different causes.

It faded. Strong for ten or twenty minutes, then gradually went soft, especially over kerbs and in long fast corners. That’s heat, almost always.

It cut out instantly. One moment full detail, the next moment the wheel is a free-spinning bit of plastic. Nothing in between. That’s a disconnect, a safety cut, or the game losing the device.

It’s weak from the start of this session but was fine last week. That’s a setting or a driver update, nine times out of ten. Something changed and it wasn’t the hardware.

Hold that distinction in your head because every section below sorts into one of those three buckets.

The fade: thermal throttling

Every wheelbase has a thermal ceiling and most of them hide what happens when they reach it. Belt-drive Logitech and older Thrustmaster units (the T300, T150, TMX) are the worst offenders. The T300 in particular will run at full strength for a while and then drop to what feels like 60 percent, and it does this silently, no light, no message. Thrustmaster’s fan is small and mostly decorative. Guys on r/simracing have been strapping 80mm case fans to the back of T300s for a decade for exactly this reason, and yes, it works.

Direct drive is better but not immune. A Moza R5 or Fanatec CSL DD at 5 to 8 Nm will get properly warm in a 45-minute ACC race at 100 percent in-game gain with the base set to maximum. The CSL DD’s firmware will pull torque back when it gets hot and Fanatec’s driver shows nothing obvious about it unless you go looking in the Fanatec Control Panel. Moza Pit House at least has a temperature readout, which is a small thing that I wish everyone did.

The quick test: put your hand on the housing. If it’s uncomfortable to keep there, that’s your answer. Stop, let it cool 15 minutes, and see if the strength comes back. If it does, you’ve found it.

The fix isn’t “buy a bigger base,” at least not first. Most people running throttled belt drives have the base at 100 percent and the game at 100 percent and are clipping constantly, which is what generates the heat. Clipping means the game is asking for more force than the motor can deliver, so it’s pinned at max output the whole time you’re loaded up in a corner. iRacing’s FFB meter (the little bar in the black box, F-key overlay) turns red when this happens. ACC has no built-in meter, which is one of my long-standing gripes with it, so people run LUT tools or just guess.

Try this on a T300 or G29: game gain at 100, but drop the overall strength so the meter only kicks into red on the biggest kerb hits. On iRacing, hit the “auto” button next to strength in the options after a few laps and it’ll set the value so you clip only at peak load. It usually lands somewhere between 25 and 40 for a belt drive, and people are shocked that it feels more detailed at lower strength. It does, because you’re no longer flattening everything against the ceiling. Less heat, more information, base stops fading. Everyone wins except the person who wanted their arms to hurt.

The instant cut: USB, power, or a safety trip

An instant loss of all force with the wheel still turning the car in-game is a different animal. The game still sees the axis but isn’t sending force, or it’s lost the device and reacquired it as a generic input.

USB first. Front panel USB ports on PC cases are garbage for this. They run through a flimsy header cable that picks up interference and they’re often wired to a shared hub internally. Plug the base directly into a rear motherboard port, and not one adjacent to a high-draw device like a VR headset or a powered hub. USB 2.0 ports are actually preferred by some manufacturers (Simucube recommends it) because the controller is simpler and less prone to the power-management nonsense that USB 3 introduces.

Speaking of which: Windows USB selective suspend. Go into Power Options, advanced settings, USB settings, and disable selective suspend. Also uncheck “Allow the computer to turn off this device to save power” on every USB Root Hub in Device Manager. This one has caused more mid-race drops than any faulty cable, and it’s especially bad on laptops.

Power supply next. Cheap or degraded bricks sag under load. A CSL DD with the 180W upgrade brick behaves differently from the 90W one, and the 90W will hit its limit at 8 Nm while the base tries to draw more. Symptom is FFB that cuts at big impacts (wall hit, heavy kerb strike) and comes right back. If you’re on a Fanatec base with the smaller brick and see this, that’s likely it. Not a defect. A limitation they don’t advertise very loudly.

Older Fanatec bases (CSW 2.5, older Podium units) are also notorious for the base rebooting itself under a power spike. You’ll hear the fan spin down and the display go blank for a second. Check that the PSU barrel plug is seated all the way; it’s a snug fit and people leave it a millimeter short.

Then the E-stop and the quick release. If you have a Simucube, Asetek, or VRS base with an emergency stop button, check that it hasn’t been bumped. Some of them latch. Also check the quick release: Fanatec’s QR1 lite on the CSL DD is a known weak point. If the rim isn’t fully seated, the base can lose contact with the rim’s electronics, throw a “no wheel detected” state, and drop FFB. The Fanatec QR2 metal upgrade solved this for a lot of people and I’d call it a required purchase rather than optional if you’re on a CSL DD and pushing above 5 Nm.

And the cable under the rig leg. I mean it. If your wheelbase USB cable routes near a pedal plate or a rig upright, check it. I lost two hours once to a cable a rig leg was sitting on top of, and it only dropped when I braked hard enough to shift the whole thing.

The “weak since this session” case: settings and software

This is the annoying one because it’s not a fault, it’s a change you didn’t make on purpose.

Per-car FFB multipliers. Assetto Corsa and Assetto Corsa Competizione both have a per-car gain that’s saved with the car. Hop into a car you haven’t run in a while and it might be sitting at 50 percent from some old experiment. In AC it’s the “+/-” on the FFB strength on the pit screen and in ACC it’s in the setup or via Content Manager’s per-car override.

iRacing’s “reduce force when parked” and the auto strength. The parked reduction is fine and you want it on. But the “auto” strength button, if you hit it accidentally after a spin or on the grid at standstill, will set a stupid value. Check your strength number in options and recognise that a base that was on 30 and is now on 12 has been “auto”-ed.

Driver or firmware updates. Fanatec is the big one here. A new Fanatec driver installs with default base settings, meaning SEN goes back to AUTO, FF goes to 100, and your tuning menu profile might silently reset if the driver version changed the profile format. Moza’s Pit House updates are less dramatic but they do occasionally reset the game-specific profiles. If you updated anything in the last week, that’s a strong suspect.

Game-side updates. ACC periodically tweaks the FFB curve. Le Mans Ultimate’s FFB has changed noticeably between builds and I’ve seen a stock-setting car go from great to numb after a patch. rF2 users have known this pain for years. Check the patch notes before you tear anything apart.

Steam Input. If you use Steam, check that Steam Input isn’t enabled for your wheel. It’ll happily hijack the device as a generic gamepad and the game gets an axis with no force channel. Right-click the game, Properties, Controller, and set it to “disable Steam Input.” This bites people on new installs constantly.

A quick word on desks

If you’re on a desk clamp and things feel weaker or vaguer than they should, it may not be the wheel. A direct drive base at even 5 Nm on a wobbly IKEA desk is losing a real chunk of its force to the desk flexing. You feel the steering flop and figure the base is getting weak. It’s the desk. A Next Level Racing Wheel Stand 2.0 or similar removes that variable for far less than a new wheelbase, and it’s the first thing I’d change before spending on a base upgrade.

Diagnosing by base: a rough map

It’s not exhaustive. But it’ll get you pointed in the right direction faster than guessing.

When it actually is the hardware

Sometimes it is. Belt-drive Logitech bases (G29, G920, G923) wear the belts and the hall sensor over years. The classic G29 death is a grinding noise and FFB that surges rather than fades, and once you’re there it’s not really worth fixing given a Logitech G923 is around $300 and a Moza R5 bundle with pedals is closer to $400 and a genuine upgrade. Thrustmaster T300 belts wear too; the symptom is a feeling of slack around center and a grinding rattle, not a total loss.

Direct drive bases basically don’t wear. If a CSL DD or R5 stops producing force and it survives every check above, it’s a driver board or PSU issue and you’re into the warranty conversation. Which brings up the elephant. Fanatec’s support and shipping reputation went from meh to properly bad through 2023 and 2024, and while Corsair’s takeover has improved it somewhat, I still wouldn’t count on a fast turnaround. Moza’s support is more responsive in my experience, though the brand is younger and the long-term reliability data just isn’t there yet. Simucube and Asetek are in a different tier for support, and you pay for it.

Before you ship anything back, though, run through the checklist again. Support departments ask you to do it anyway.

FAQ

Why does my force feedback get weaker the longer I play? Heat. Your base is throttling to protect the motor. Drop the strength so you’re not clipping constantly, add airflow if you can (a case fan on the back of a T300 is a genuine fix), and stop running everything at 100.

Why did my wheel suddenly lose force feedback but still steer? The game still sees the steering axis but has lost the force channel, which usually means a USB power-management drop, Steam Input grabbing the device, or the base reset itself under a power sag. Disable USB selective suspend, plug into a rear motherboard port, and check Steam’s controller settings for the game.

Does force feedback stop working when the wheel gets too hot? It reduces, it doesn’t stop entirely on most bases. Fanatec and Thrustmaster both taper output as temperature rises. A total cutoff from heat is rare and suggests the base actually hit a hard protective shutdown, in which case give it 20 minutes and lower your settings before running again.

Check this before you order anything

Don’t buy a new base because the old one went weak. Run these in order: touch the housing for heat, drop in-game strength until you’re only clipping on big hits, move the USB to a rear motherboard port and kill selective suspend, disable Steam Input for the game, and open your driver panel to confirm the base is on your saved profile and not fresh defaults.

If it’s still dead after all that, then think about hardware. If you’re on a G29 or T300 that’s five years old and belt-worn, the Moza R5 bundle at around $400 is the sensible replacement and you’ll never think about thermal throttling again. If you’re already on a CSL DD and it’s cutting under load, buy the 180W power supply (or the QR2 if the rim wiggles) before anything else. Both are far cheaper than the conclusion most people jump to.