FFB troubleshooting: dead, weak, or oscillating force feedback

Force feedback failures almost always announce themselves as one of a handful of symptoms: no FFB at all, FFB that works then fades, FFB that cuts in and out, a wheel that oscillates or bounces, FFB that feels heavy but vague, FFB that dies when a third-party app is running, or FFB that broke right after an update. Each has a different first move. Match your symptom below and work its steps: each one names what to rule out and which detail page to open next.

Before anything else, know your variables. When you ask for help, or before you start changing settings, write down five things: the wheelbase model, the platform (PC, PS5, Xbox), the sim, the driver/firmware version, and whether another sim still has FFB. That last one splits every problem in half: if FFB is fine in another title, the base is healthy and the fault is the sim’s settings or a patch.

Symptom 1: no FFB, but steering still works

The wheel turns the car, buttons work, the motor is silent. Steering angle and motor torque are independent, so this is normal and recoverable. Work outward from the hardware:

1. Test the base. Open Pit House, Fanatec Control Panel, TrueDrive, or G Hub and run the test/spin function. No force there means the problem is hardware, driver, or power, so stop chasing sim settings.
2. Check power. Direct drive bases have a power brick and many have an e-stop or a power button that can sit half-engaged. Reseat the power connector and the emergency stop.
3. Check USB. Plug straight into a rear motherboard port. Remove hubs and extensions (see Symptom 3).
4. Reinstall drivers. A failed firmware flash or a Windows update can leave the base detected but inert, so roll back or reinstall the drivers and firmware.
5. Open the controller panel. Run joy.cpl in Windows and confirm the wheel is detected and the axes move.
6. Check the sim toggle. Some sims ship FFB disabled on a fresh controller profile, and a corrupt per-car profile can read as zero force, so verify the master FFB toggle and per-car profile.
7. Recalibrate. On Logitech wheels especially, FFB and centering can break after the PC sleeps or after a crash; recalibrating in the Logitech app restores normal behavior.
8. Check third-party apps. One may be mid-handoff (see Symptom 6).

If one sim is the only one without FFB, jump to Symptom 7 (update bugs) and your per-sim settings.

Symptom 2: weak FFB, or FFB that fades after 20–45 minutes

There are two very different causes, and the recovery time tells them apart.

• Thermal derate. Force fades over a long stint, the base is warm to the touch, and it recovers slowly over several minutes of cooling. This is not a fault: the firmware cuts torque to protect the motor. Drop wheelbase strength to 70–80%, kill static damper/friction/inertia, make sure you aren’t clipping, and add airflow. Full diagnosis and the recovery-time test are on wheelbase overheating.
• Initialization glitch. FFB is weak from the start, or it loads at quarter strength and snaps back to full the instant you reset the car or reload the session. This is not heat, which never recovers instantly. The cause is an initialization or software glitch, or simply low gain. Re-run the sim’s strength setup and check the per-car scaling. In iRacing, hit Auto on a representative lap; see per-sim settings.

If a base advertised at a given torque cannot sustain normal forces and still derates after you’ve lowered strength, cooled it, and fixed clipping, log the temperature and escalate a warranty case.

Symptom 3: FFB cuts in and out, or the base disconnects under load

Intermittent FFB that drops alongside your haptics or transducers is almost always USB or power, not a setting. The base is briefly leaving the system.

1. Plug the wheelbase into a rear motherboard USB port, not a front-panel port, hub, or extension.
2. Remove every hub and long USB extension.
3. Add devices back one at a time until the dropout returns; the last one you added is overloading the controller or the power budget.
4. Watch PC load: a maxed-out system can starve USB polling.

A hardware vendor will often insist this is the sim’s fault. It usually isn’t: a base that disconnects from the operating system is a power/USB problem the sim can’t cause.

Symptom 4: the wheel oscillates, shakes, or bounces

Separate normal self-aligning torque from a runaway loop. Oscillation is worst hands-off, on straights, in light cars, and at low FFB, because the motor torque and the sim’s centering spring chase each other.

• General oscillation. Keep a hand on the wheel (it damps for free), then fix it least-detail-lost first: small inertia, small friction, center/low-speed damping, reduced in-sim road texture, lower wheel-rotation speed. Full recipe on filters and smoothness.
• Violent bounce at lock. This shows up at full steering lock, commonly on high-torque DD bases in BeamNG: the soft lock is rebounding instead of stopping. Adding resistance/damping at the lock makes it feel like a wall rather than a spring.
• Wheel fights you. If the wheel pulls or fights you the wrong way, check the inverted FFB toggle. An inverted steering axis makes the wheel drive away from center instead of self-centering. In BeamNG the fix is the inverted checkbox under the steering axis.
• Third-party app. Apps like MAIRA can introduce violent oscillation if overall scale, detail, and output limits are set too high. Calm it with base-side damping/friction/inertia and retest per car rather than only lowering all strength.

Symptom 5: FFB feels heavy but vague, you’ve lost detail

Strong, effortful, and dead. The wheel stays pinned at full force mid-corner instead of lightening as the front lets go, and kerbs feel the same as cornering load. That is clipping: the sim is asking for more force than the base can output, so the peaks flatten. The fix is one rule: set base strength to 100% (or your true Nm in iRacing’s Wheel Force) and lower the in-game gain until the peaks stop pinning. More Nm raises the ceiling before clipping, but a high enough gain still clips any base. Full detection-per-sim and starting points are on FFB clipping.

If instead the wheel feels mushy and numb in the center, that’s over-filtering, not clipping. Back off damping, friction, and smoothing one at a time on filters and smoothness.

Symptom 6: FFB dies when a third-party app is running

irFFB, MAIRA, and similar tools sit between the sim and the base, so they add their own failure point. The usual signature is FFB that works until a session-state change (qualifying to race, or arriving on the grid), then goes dead until you restart the app.

• Restart the app at the point it drops, or remove its startup hooks.
• Better: return to native FFB. Re-enable the sim’s own FFB, exit and reload the session, remove the app’s startup entries, and verify your native settings (in iRacing, confirm 360 Hz FFB and Wheel LFE). On a modern DD base most drivers no longer need irFFB; see MAIRA and irFFB.

Symptom 7: FFB broke right after a sim or driver update

If FFB died in exactly one title the day it patched, and other sims are fine, the bug is game-side, and reinstalling hardware drivers won’t fix it. Reported cases include ACC on Xbox losing FFB across wheels broadly after an update, and F1-title patch regressions. Check the platform’s patch notes and community threads before you start swapping USB ports.

Some update fixes live in config files rather than menus. On Moza bases that lost FFB in iRacing, setting enableFFB360HzInterpolated to 0 in app.ini has restored it; see per-sim settings for the iRacing config details.

When it’s the hardware

Escalate a warranty or support case only after you’ve ruled out settings, power, and USB. Grinding noises, a base that never produces force in its own software, or advertised torque it cannot sustain even cool and unclipped are real faults. Normal traits are not: gear-driven Logitech wheels clack, compact DD bases run warm, and aggressive settings cause oscillation. The wheelbase drivers and troubleshooting page covers the hardware side; the pages linked above cover the FFB side.