iRacing Simucube Settings: TrueDrive, Recon Filter & Paddock Profiles

I’m a sim racer and amateur racer with a passion for Motorsport, good racecraft and the technical and setup aspect of sim racing.

The first time I drove a Simucube SC2 Pro in iRacing, I left the Reconstruction Filter at zero and lasted about three laps at Watkins Glen before I switched it back on. The signal was raw, immediate, and absolutely vicious over the kerbs at Turn 5. By lap three my forearms were burning. That’s the Simucube sim racing experience in a nutshell – more honest, more demanding, more rewarding than any other DD brand, with absolutely no tolerance for setup laziness. The good news for iRacing specifically is the setup itself isn’t complicated. Two settings carry 90% of the weight: Reconstruction Filter in TrueDrive (somewhere between 1 and 3 depending on temperament), and the in-game Wheel Force value matched exactly to your base’s real Nm output. Get those two right and the rest is fine-tuning.

The 2026 wrinkle worth flagging up front: iRacing’s native 360Hz FFB rollout introduced a bug for some Simucube users where the signal felt rubbery, grainy, or oscillated for no obvious reason. It’s well-known in the community by now, well-understood, and well-fixed (TrueDrive 2024.5 or newer, “iRacing 360Hz” flag enabled in the profile). If your wheel feels off and you haven’t updated TrueDrive recently, that’s almost certainly why.

TrueDrive setup for iRacing

The Reconstruction Filter is Simucube’s predictive smoothing algorithm. It looks at the incoming FFB stream and fills in the gaps between samples – which sounds invisible until you realise iRacing’s physics engine, even at 360Hz, can feel slightly grainy when fed straight to a 25Nm motor at full strength. Recon Filter at 1 keeps the signal as raw as possible. You feel everything – which sounds great in theory and quite often is in practice, but it also means you feel every imperfection in iRacing’s surface mesh. Some kerb sequences just become noise. Recon Filter at 3 smooths that without softening the slip-angle information you actually use. Filter at 5 is too much smoothing for most cars and most users.

My take after a few months on the Pro in the post-360Hz era: start at 0 or 1. The 360Hz signal doesn’t need much smoothing – the old 1-vs-3 debate is largely settled toward the lower end now. If kerbs feel genuinely harsh after a stint, bump to 2. Only go to 3+ if there’s specific oscillation you’re trying to mute.

Setting	SC2 Sport (17Nm)	SC2 Pro (25Nm)	SC2 Ultimate (32Nm)
Overall Strength	100%	100%	100%
Steering Range	900-1080°	900-1080°	900-1080°
Reconstruction Filter	3	3	3-4
Damping	15-20	10-15	10
Friction	5-10	5	5
Inertia	5	5	5
Slew Rate Limit	Off	Off	Off
iRacing 360Hz Mode	Enabled	Enabled	Enabled

The Damping and Inertia numbers above are baseline rather than gospel. Heavier wheel rims (320mm formula or GT3 weights with quick-release adapters) feel better with slightly less Damping, lighter rims with slightly more. The Ultimate at 32Nm benefits from a touch more Recon Filter than the Pro because there’s more raw torque to smooth – same reasoning as why a louder amp needs a better noise floor.

In-game iRacing settings

This is the part of the setup people overcomplicate. Wheel Force matches your base’s actual Nm output – 17, 25, or 32. Damping stays at 0 (TrueDrive handles it). Min Force stays at 0 (this is a DD, there’s no centre slack to bridge). Linear Mode ticked (raw 1:1 telemetry). Then you Auto-calibrate Max Force per car. Done.

Setting	SC2 Sport	SC2 Pro	SC2 Ultimate
Wheel Force	17 Nm	25 Nm	32 Nm
Strength	100%	100%	100%
Damping	0%	0%	0%
Min Force	0%	0%	0%
Use Linear Mode	Yes	Yes	Yes
Max Force GT3 after Auto	~45 Nm	~50-55 Nm	~55-60 Nm

One Wheel Force trap worth flagging because it catches almost everyone the first time. If you cap TrueDrive at 50% for safety or comfort (12.5Nm on a Pro), you must drop iRacing’s Wheel Force value to match. 12.5Nm, not 25Nm. Mismatch the two and you’ll either clip savagely on heavy corners (Wheel Force set too low for the real output) or feel lifeless and hollow (Wheel Force set too high – iRacing is throttling the signal to a ceiling that doesn’t exist). The fix takes thirty seconds. The frustration of trying to debug the symptom without knowing the cause takes weeks.

Morad vs Suzuki – the Paddock profile debate

TrueDrive Paddock is the cloud-shared profile ecosystem. By 2026 the two most-downloaded profile authors are Daniel Morad and Dan Suzuki, and their philosophies sit at opposite ends of the spectrum. This is genuinely interesting because it’s not a “one is right” debate – both work, both have a real following, both produce fast drivers. They just optimise for different things.

Daniel Morad is a real-world GT3 driver. His profiles aim for 1:1 realism with whatever a Bentley Continental’s actual steering rack would do at Sebring. Low slew rates. Minimal artificial damping. High force. Heavy, mechanical, slightly viscous. Immersive in the absolute sense of the word – in a stint it’s a workout, and you’ll feel every detail of the car’s behaviour. Morad’s profiles teach you to drive the car the way the car wants to be driven, which is the whole point if your goal is to bridge to a real seat one day.

Dan Suzuki built his reputation on iRating consistency and the pace-saving philosophy that comes with it. His profiles add more software damping and a touch more friction. Straight-line oscillation gets tamed. Snap oversteer gets the predictability boost it needs to be catchable lap after lap, hour after hour. You’ll lose some of the sharpest tactile information about the car’s underlying behaviour, but you’ll also lose four wrecks per week.

Which to pick? Honest answer: it depends on what you’re optimising for. If iRating is the goal, Suzuki. If immersion and real-world technique transfer is the goal, Morad. Both are widely respected. Both are excellent starting points. The rule that’s stuck in the Simucube community is to use a Paddock profile as the baseline and then tweak from there. Your wheel rim weight (a 320mm GT3 rim feels very different from a 290mm formula rim) plays a meaningful role in how inertia translates, and a profile built around someone else’s hardware won’t be perfect on yours.

The 360Hz iRacing FFB bug fix

When iRacing rolled out native 360Hz FFB output a couple of years back, Simucube users got incredible detail and signal density. Some users also got a strange new bug – the wheel started feeling rubbery, faintly grainy, prone to oscillation that hadn’t been there before. It wasn’t a Simucube hardware issue. It was an API timing mismatch between iRacing’s new output rate and the older TrueDrive runtime.

The fix is mostly firmware-side:

Run TrueDrive 2024.5 or newer. This patches the API timing delay between iRacing and the wheelbase. Older versions are the source of the bug.
Ensure the “iRacing 360Hz” mode flag is enabled in TrueDrive’s iRacing-specific profile.
If the wheel still feels grainy after both of those, bump Reconstruction Filter to 4 and add 5-10% DirectInput Damping to settle the high-frequency motor resonance.

Loading products...

Common Simucube + iRacing mistakes

Wheel Force value mismatched to actual TrueDrive output. If you’ve capped TrueDrive at 50% for comfort, drop iRacing’s Wheel Force to match. Mismatching causes either clipping or lifeless feel – both feel equally wrong.
Reconstruction Filter at 0 or off. iRacing’s signal genuinely is too raw for some kerb sequences without at least Filter 1. Sub-1 is for masochists. Run 3 if you want a polished signal, 1 if you want everything.
Old TrueDrive on 360Hz iRacing. The pre-2024.5 timing bug is real. Update first, troubleshoot second.
Min Force above 0. Robotic centre rattle. 0% always on Simucube. There’s no centre slack to bridge.
Linear Mode unticked. Raw 1:1 telemetry is the whole point of a 25Nm DD. Always ticked.
Treating a Paddock profile as final. Use one as a baseline, then tweak. Your wheel rim isn’t the profile author’s wheel rim, and the difference matters more than people expect.

The Simucube + iRacing combo punches well above its setup complexity. Get Reconstruction Filter and Wheel Force right, pick a Paddock profile that suits how you want to race rather than what other people say is “correct”, and the rest is fine-tuning. The wider iRacing matrix is iRacing FFB settings, the FFB concept layer is the force feedback explainer, and if you’re still researching the SC2 lineup, the wider DD picture is in our direct drive wheel buyer’s guide.

Sources: Daniel Morad TrueDrive Paddock community profiles, Dan Suzuki TrueDrive Paddock community profiles, Granite Devices Simucube official forums, r/iRacing Simucube setup discussions, TrueDrive 2024.5+ release notes.