MAIRA and irFFB for iRacing: do you still need them?

iRacing now ships native 360Hz force feedback with wheel LFE, and that single change rewrote the answer to “do I need a FFB app.” For the core steering signal on a direct drive base, the answer is mostly no. These apps still come up in nearly every FFB thread because MAIRA adds something iRacing does not: a tunable detail boost. irFFB mostly solved a problem iRacing has since solved itself.

What each app actually does

irFFB reshapes iRacing’s force feedback. It can feed the 360Hz steering-column torque to your wheel, upsample and filter the standard 60Hz output, and layer telemetry-driven effects like suspension load and understeer cues. It existed because iRacing’s FFB used to be a 60Hz signal that felt coarse on direct drive and thin on belt and gear wheels. That is no longer true. The original repo’s last release was October 2018, so treat classic irFFB as legacy — a community fork is the only actively-maintained option, and on a modern base you almost certainly do not need it.

MAIRA (Marvin’s Awesome iRacing App) is a different tool. It reads live iRacing telemetry and adds tunable force feedback detail, pedal haptics, and optional wind and seat-belt-tensioner kits. It is a standalone Windows app — the FFB and pedal-haptics core needs no SimHub, though the Typhoon wind and seat-belt kits hook into it for hardware control. MAIRA is completely free; the author states plainly that he will never charge for it. The current build is MAIRA Refactored 2.x; the classic 1.x app is deprecated.

Do you actually need them on a direct drive base?

The community splits cleanly, and the split is worth understanding first.

On the “yes” side, MAIRA’s detail slider is the draw. Drivers on strong bases like the Moza R16 describe MAIRA plus iRacing’s wheel LFE as the best feel they have had in any sim, running the detail boost around 300% with otherwise neutral base settings. The effect is strongest on GT3 and other sports cars, which produce relatively low self-aligning torque, so the extra detail surfaces road and grip texture that the stock signal leaves flat.

On the “no” side, plenty of capable racers tried MAIRA and could not tell a difference, or felt it “just added noise.” That camp skews toward open-wheelers, which already generate aggressive, information-rich FFB where an added detail layer muddies more than it reveals. A common verdict is that an 8Nm CSL DD on stock iRacing FFB is already good, and MAIRA is a refinement, not a fix.

The fairest summary: if you run sports cars and want more texture, MAIRA is worth ten free minutes. If you run formula cars or you are happy with stock, skipping it costs you no speed. Either way, get your base FFB tuning right first — MAIRA cannot rescue a clipping signal or a wrongly-set Wheel Force.

The oscillation fix everyone gets wrong

The single most-reported MAIRA problem is the wheel shaking violently when you take your hands off or grip too lightly. It looks like a bug. It is almost always a settings mistake, and the fix is specific.

Leave Output Maximum at its default (near 50). Do not set it to your wheel’s Nm. This is the trap. People see “Output Maximum” and a number around 50, assume it should match their 15Nm base, and lower it to 15. That divides the entire signal by roughly 3.3x, so the wheel goes weak, so they crank Overall Scale to enormous values to get force back — and a wildly over-scaled signal is exactly what feeds the oscillation loop. Restore Output Maximum to default and Overall Scale drops back to sane territory immediately.

From there, dial it in like this:

1. Output Maximum: default (~50), untouched. Treat it as plumbing, not a power knob.
2. Overall Scale: start low and climb. Use the app’s hotkeys (or the auto button, the “A” next to Overall Scale) on a track you know, raising it until the weight feels right without clipping. On a strong DD this lands far lower than people expect — single digits to low double digits, not 60.
3. Detail / Feedback Detail: start near 0 and add to taste. Several drivers report SimPro and similar interactions feeling granular and harsh with feedback detail left high; bring it down, then add the detail boost separately for the texture you want.
4. Add mechanical damping, friction, or inertia in your base software. A small inertia or damping bump in Pit House, SimPro, True Drive, or Fanatec’s tuning menu kills the residual oscillation while adding a little weight, the same fix that works for hands-off shake without MAIRA.

The mechanism is the same one behind all FFB oscillation: the motor torque and the sim’s centering force chase each other through the signal latency, overshooting and correcting. Keeping a hand on the wheel damps it for free. Over-scaling the signal makes it explode.

A sane starting point

Set your base to its rated peak and your in-sim iRacing FFB correctly first — Wheel Force at your base’s true Nm, Min Force at 0 on a DD, and the per-car Max Force set with the auto button on a representative lap. iRacing’s own Controller Setup and Calibration guide is the authority on those. Only then add MAIRA, with Output Maximum at default, Overall Scale low, and detail near zero, and build up one slider at a time.

If you are on a belt or gear wheel like a G923 or T300, MAIRA’s payoff is more obvious — drivers describe an immediate detail jump and suddenly feeling differential grip side to side. It will not turn a geared wheel into a direct drive or remove physical gear cogging, but it gives you more usable signal to work with.

MAIRA also overlaps with the broader stack of iRacing companion apps — its wind and seat-belt kits compete with SimHub-driven setups, its pedal haptics with bass shakers. If you only want FFB detail, ignore those modules and run the standalone app on its own.

Crashes and quirks

MAIRA Refactored is stable for most users, but a few quirks recur. Some drivers see the wheel recenter or spin on joining and leaving sessions (notably on Moza), and there are reports of mid-race crashes or an auto function that will not turn off. These are app behaviors, not iRacing faults — keep the app on the current 2.x build, and if a feature like auto-scale fights you, map it to a clean hotkey and trigger it deliberately rather than leaving it running.