Skip to content

FFB settings by sim: iRacing, ACC, LMU, AMS2, AC

Set your wheelbase software to 100% (or peak/linear) once, then tune force feedback inside each sim. Every engine sends torque differently, so the settings that feel right in iRacing are wrong in AMS2, and a custom file that fixes Assetto Corsa does nothing in ACC. Here is the correct approach for each.

iRacing sends per-wheel physical torque with no LUT, so two controls do the work: Wheel Force and Max Force.

Wheel Force is the calibration ceiling in Nm. Set it to your base’s true output, or cap it lower for headroom — running 8-10 Nm on a generic 15 Nm mid-range base (a Simagic Alpha EVO at 12 Nm or the Fanatec ClubSport DD+ at 18 Nm, for example) leaves room before the motor maxes out. Click the “Strength” label to switch the units to Nm.

Max Force is the per-car saturation point and the number that actually scales feel. It changes between cars: a GT3 might want Max Force in the low 40s, while a light open-wheeler like the FF1600 drops to ~10 because it generates far less self-aligning torque. Hit the Auto button on a representative lap and iRacing sets Max Force from your driving; the Strength % slider only matters at the moment you click Auto.

Leave Min Force at 0 on a direct drive base. Per iRacing’s Controller Setup and Calibration guide, Min Force only exists to push past the deadzone in belt and gear wheels (G29/G920, some Thrustmaster). Leave in-sim smoothing and damping at 0 and use your base’s own filters instead.

iRacing’s signal now updates at 360 Hz with native wheel LFE/seat-of-pants effects, which closed most of the old gap. irFFB and MAIRA (Marvin’s Awesome iRacing App) are optional external tools that inject suspension and LFE detail; modern DD owners mostly do not need irFFB anymore. Note the active build is MAIRA Refactored 2.x — the classic MAIRA 1.x is no longer updated, and the original irFFB is largely unmaintained (community forks exist).

ACC’s FFB is complete out of the box — no custom files. Gain is the master output: raise it until the wheel clips on the highest-load corners, then back off a few percent. Min Force is deadzone compensation for cheap belt/gear wheels, so leave it 0 on a DD and use a small single-digit value only on something like a G29.

Dynamic Damping is front-axle load resistance — run it at 100 on a DD, lower on entry-level wheels that already feel heavy. Road Effects is artificial kerb and surface texture; add it to taste, and keep it low on a DD that already surfaces that detail. Match your in-sim steer lock to your base (1080 is typical).

LMU runs the rFactor 2 engine with physics-derived FFB at a high sample rate, so it is detailed but easy to under-gain. 35% in-sim gain is too low — raise it and accept slight clipping on the peaks to lift the low-signal detail, or watch the channel with an FFB meter and dial it back from there. A per-car FFB multiplier lets you balance cars that load the wheel differently.

Some bases (VRS DirectForce Pro, Simucube, Asetek) expose Telemetry FFB, which reads the sim’s exported channels for richer gear-shift and kerb effects. Owners of those bases consistently rate it as the standout FFB experience, especially in LMU.

AMS2’s default FFB feels floaty and slippery because of its Madness/Project CARS 2 engine. The community fix is a custom FFB file dropped in the documents folder, which replaces the whole force curve. The big ones are rFuktor (the “Ultimate Evo Tune by Kuku” and “Reallife focused by Thirty-Four” variants) and danielkart V7000, hosted on overtake.gg and the Reiza forum’s ~400-page custom FFB collection thread.

In-sim you get three modes: Default, Default+, and Custom — pick Custom to load the file. Also turn camera movement off and raise tire audio, which kills a lot of the “floaty” perception. Note that 1.6.x updates improved the stock FFB enough that some drivers run Default+ now and skip the file entirely.

AC ships with minimal in-sim FFB — a Gain plus a few effect sliders (kerb, road, slip, ABS) — and feels light or numb at the limit. The real fix is a LUT file: run WheelCheck and a LUT generator to linearize a cheap wheel and recover low-force detail, then set Gamma to 1 and apply Min Force through the LUT rather than the slider.

Turn the artificial effect sliders off or very low — they are canned vibration, not real road feel. Use the in-game FFB Clip app to watch live clipping, and add Custom Shaders Patch (CSP) if you want extra FFB options. The big torque numbers come from your base, not from AC.

SimMaster controlMin ForceCustom file?Clip check
iRacingWheel Force + per-car Max Force (Auto)0 on DDNo (irFFB optional)Auto button
ACCGain (clip then back off)0 on DDNoBy feel
LMUIn-sim gain (don’t undergain)0 on DDNoFFB/telemetry meter
AMS2Custom FFB filen/aYes (rFuktor / danielkart)By feel
ACGain + LUTVia LUTLUT, not full fileFFB Clip app

Frequently asked questions

What are the correct iRacing FFB settings for a direct drive base?

Set Wheel Force to your base's true output in Nm (click the 'Strength' label to switch units to Nm), leave Min Force at 0 on a DD, and let per-car Max Force scale the feel — hit the Auto button on a representative lap and iRacing sets it from your driving. iRacing now sends physical per-wheel torque at 360 Hz with native LFE/seat-of-pants effects, so leave in-sim smoothing and damping at 0 and use your base's own filters instead.

Do I still need irFFB or MAIRA on a modern direct drive base?

Mostly no for the core signal — iRacing's 360 Hz native FFB closed most of the old gap, and modern DD owners mostly do not need irFFB anymore. irFFB and MAIRA (Marvin's Awesome iRacing App) are optional external tools that inject suspension and LFE detail. Note the active app is MAIRA Refactored 2.x; the classic MAIRA 1.x is no longer updated and the original irFFB is largely unmaintained.

Why does AMS2 feel floaty, and do I need a custom FFB file?

AMS2's default FFB feels floaty and slippery because of its Madness/Project CARS 2 engine. The community fix is a custom FFB file (rFuktor variants like 'Ultimate Evo Tune by Kuku' or 'Reallife focused by Thirty-Four', or danielkart V7000) dropped in the documents folder, with the in-sim FFB mode set to Custom. Also turn camera movement off and raise tire audio. Since the 1.6.x updates improved the stock force model, some drivers now run Default+ and skip the file entirely.

What FFB gain should I run in ACC and LMU?

ACC is complete out of the box with no custom files — raise Gain until it clips on the highest-load corner, then back off a few percent, run Dynamic Damping at 100 on a DD, Min Force at 0, and keep Road Effects low. LMU runs the rFactor 2 engine and is easy to under-gain: 35% in-sim gain is too low — raise it and accept slight peak clipping, and use Telemetry FFB if your base (VRS, Simucube, Asetek) supports it.