When the wheel spins freely with zero resistance, the base hardware is almost always fine and force feedback simply is not flowing. The fastest single test I run is to open the manufacturer’s tuning menu and feel for the base’s static centering spring, the self-centering pull you get even with no sim running. If that spring is present, the motor and driver work, and the fault lives in the sim’s settings or the base’s mode. The fix order from there: confirm the base works, enable FFB inside the sim on the correct device, check the base is not in a compatibility mode that mutes FFB, then restart the driver’s FFB service if it has crashed.
No force feedback is one of the most demoralising faults because a wheel without FFB feels like driving a broken toy, yet it is almost never a broken base. Across the direct-drive and belt-drive bases I have bolted to rigs over the years, the cause has been a sim setting, a mode toggle, or a stalled driver service far more often than any hardware failure. This spoke owns the “no FFB at all” fault specifically. If FFB is present but feels wrong, notchy, or weak, that is a different layer covered in Fixing Notchy or Grinding Force Feedback, and the full fault map is on the troubleshooting hub.
First, Prove the Base Works
Before you touch a sim, prove the base can produce force at all. Open the manufacturer’s driver app and its tuning menu, then feel the rim. A healthy base produces a static centering spring the moment it is powered and recognised, pulling the wheel gently back to centre even with no game loaded. Some apps also have a test tone or a constant-force test you can trigger from a button. If the rim resists and self-centres, the motor, the encoder, and the driver service are all working, and you have eliminated hardware in under a minute.
If the rim is completely lifeless, no spring, no resistance, then the problem is below the FFB layer. Check that the base is detected in Windows Game Controllers, that its driver app sees it, and that the base is not stuck in a firmware limbo. A base that the app cannot see at all will never produce FFB, so follow the detection fault path in Sim Wheel Not Detected in Game before you chase FFB settings. FFB cannot flow to a device the PC does not know is there.
Enable Force Feedback in the Sim
Once the base is proven good, the next and most common cause is simply that the sim’s FFB is off or pointed at the wrong device. Every title hides the enable toggle in a slightly different place, and every one of them has tripped me up at least once. In iRacing, open Options, then Controls, and confirm the Enable Force Feedback box is checked and the correct wheel is selected as the active controller. In Assetto Corsa Competizione, open Options, Controls, Force Feedback, and make sure the Enable toggle is on and the device selected is your base, not a gamepad the game auto-picked. In AMS2 the Force Feedback section lives under Controls and Bindings, with its own enable switch and a gain value that can be set to zero by accident.
The trap that catches experienced racers is device selection after a USB re-enumeration. A Windows update or even replugging the base can hand it a new address, and the sim keeps trying to send FFB to the old device. The base works in the tuning menu but the sim shows nothing. The fix is to re-select the controller in the sim’s options and save, which clears the stale assignment every time. I lost a whole evening to exactly this after a Windows update once, reinstalling the driver and even reflashing the base firmware before I noticed iRacing was still addressing the old device. A single re-select brought the wheel back to life. If you have just updated Windows or moved the base to a new port and FFB vanished overnight, this is the first place to look.
The Compatibility Mode Trap
Many wheelbases ship with a compatibility or platform mode that changes how they identify themselves to the host, and the wrong mode silently mutes force feedback on PC. A base in a console compatibility mode may enumerate and even produce a centering spring in its own app, but the sim cannot drive its FFB because the device is presenting itself as a different class of controller. The symptom, FFB dead in every title while the base clearly works on its own, is the signature of this trap.
The fix is a mode toggle, usually a button combination on the base or a setting in the driver app, that switches the base into its native PC mode. The exact combination differs by manufacturer and is worth confirming against their current documentation rather than guessing, because holding the wrong buttons can put the base into a bootloader state. After switching, the base re-enumerates and the sim sees the correct device class. I keep my daily base locked in its native PC mode and never toggle it, because a mode change at the wrong moment is exactly the kind of thing that turns a quick session into an evening of diagnosis.
The Driver FFB Service Crashed
The manufacturer’s driver runs a background service that takes the sim’s FFB signal and translates it into motor commands. That service can stall or crash independently of the app, especially after the PC has slept, after a Windows update, or when another program has grabbed the device. The result is a base that looks fine in the app but produces no force in any sim, which is genuinely confusing until you know the pattern.
The clean fix is to close the sim, exit the driver app completely from the system tray, then restart the app and its service. If the base is one that runs as a Windows service, restarting that service from Services or simply rebooting the PC clears a stalled service more reliably than anything else. The habit I follow on my rig: if FFB is dead across every title but the base passes its tuning-menu test, I restart the driver service before I change a single setting, because a stalled service will defeat every setting change you make and waste an hour.
Gain at Zero, or a Steering Lock Mismatch
Two settings quietly reduce force feedback to nothing without turning it off outright. The first is a master FFB gain left at zero, either from a fresh profile, a reset after a title update, or an accidental adjustment. A gain of zero is not “low force feedback,” it is no force feedback, and it is easy to overlook because the enable toggle is still on. The second is a steering lock or rotation mismatch so extreme that the sim never commands force in the range you are using. If the base is set to a huge rotation and the sim expects a small one, the active range can land outside where you actually drive and the FFB feels absent.
Set the master gain to a sensible starting value rather than zero, and match the base’s rotation to what the sim expects for the car. On my telemetry overlay, a gain-at-zero fault shows up as a perfectly flat FFB trace at the baseline no matter what I do on track, which is the confirmation that the signal itself is gone rather than weak. From a working baseline you can dial gain up to taste, but you cannot tune force feedback that is not there.
When No FFB Means a Hardware Fault
I keep this section short because it is the rare outcome, but it exists. If the base produces no static centering spring in its own tuning menu, if the driver app cannot see it, and if a fresh driver install and a firmware check do not bring it back, then the fault is genuinely inside the base, most likely the power supply, the motor wiring, or the controller board. The swap test, moving the base to another PC or a known-good base to yours, confirms it definitively, and that is the point at which a support ticket or RMA is the right move rather than more setting changes.
One genuine hardware signature to respect: a base that produced strong FFB and then suddenly smells of hot electronics and gives nothing is a failed component, not a settings problem. Unplug it immediately and do not keep cycling power hoping it returns. For everything else, the layers above resolve no-FFB faults the overwhelming majority of the time.
Frequently Asked Questions
Why is there no force feedback on my sim wheel?
Confirm the base works by feeling for its static centering spring in the tuning menu. If that is present, the fault is in the sim: enable FFB, select the correct device, and check the base is not in a compatibility mode that mutes FFB on PC. Restart the driver FFB service before changing settings.
How do I enable force feedback in iRacing?
Open Options, then Controls, and check the Enable Force Feedback box. Make sure your wheel is selected as the active controller. If FFB vanished after a Windows update or a port change, re-select the controller to clear a stale USB assignment that points the sim at the wrong device.
Why does my wheel have no force feedback in ACC?
In ACC, open Options, Controls, Force Feedback, and turn the Enable toggle on with your base selected as the device. A base stuck in a console compatibility mode will enumerate but produce no FFB in ACC, so switch it to native PC mode if the tuning-menu spring works but the sim does not.
How do I know if my wheelbase is broken or FFB is off?
Open the manufacturer tuning menu and feel for the static centering spring. If the rim resists and self-centres with no game running, the base works and FFB is a settings or driver-service issue. Only if the spring is absent and a driver reinstall plus firmware check fail is the hardware suspect.
How do I restart my wheel driver FFB service?
Close the sim, exit the driver app fully from the system tray, and relaunch it. If the driver runs as a Windows service, restart that service in Services or reboot the PC. Restarting the service before changing settings is the fastest fix when FFB is dead across every title.
