iRacing Simucube Settings: TrueDrive + In-Game for 2026

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 two settings that matter most for Simucube on iRacing aren’t in the in-game menu – they’re in TrueDrive. Reconstruction Filter at 3 is the community sweet spot for most drivers; raise to 4 if you’ve got the 360Hz FFB rubbery-feel bug. And the Wheel Force number in iRacing must match your base’s real output Nm (17 for Sport, 25 for Pro, 32 for Ultimate). Get those two right and the rest tunes itself.

Quick Navigation
TrueDrive setup | In-game iRacing | Morad vs Suzuki profiles | 360Hz bug fix | Common mistakes

TrueDrive setup for iRacing

Simucube on iRacing benefits from TrueDrive’s Reconstruction Filter – the predictive algorithm that smooths iRacing’s slightly grainy physics engine output without adding latency. Most drivers settle on 3 as the sweet spot. Set it to 1 and you get raw, immediate telemetry (great for catching micro-slides, less great over rough kerbs). Set it to 4 or 5 and you tame the high-frequency motor resonance that sometimes triggers the 360Hz “rubbery” feel.

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

In-game iRacing settings

The in-game side is straightforward once TrueDrive’s right. Wheel Force matches your base’s real Nm output. Damping stays at 0 (TrueDrive handles it). Min Force stays at 0 (Simucube is DD, no centre slack). Linear Mode ticked (raw 1:1 telemetry). Max Force gets calibrated per car via Auto.

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 (Auto)	~45 Nm	~50-55 Nm	~55-60 Nm

One Wheel Force trap worth flagging: if you cap TrueDrive at 50% (e.g. 12.5Nm on a Pro for comfort or safety), you MUST drop the iRacing Wheel Force to match (12.5 Nm). Mismatching causes either savage clipping on heavy corners or a lifeless, hollow feel.

Daniel Morad vs Dan Suzuki – the profile debate

TrueDrive Paddock is the cloud-shared profile ecosystem and the two most-downloaded creators are Daniel Morad and Dan Suzuki. They take opposite approaches.

Daniel Morad is a real-world GT3 driver. His profiles aim for 1:1 realism with low slew rates, minimal artificial damping, and high force – the heavy, viscous mechanical feel of an actual race-prepped steering column. Immersive, but it’s a workout over a stint.

Dan Suzuki is the sim-racing-pace specialist. His profiles add more software damping and friction to tame straight-line oscillation, with predictable snap-oversteer behaviour that makes catching slides easier. Built for iRating retention more than realism.

The rule from the Simucube community: use a Paddock profile as a starting baseline, then tweak. The physical weight and diameter of your specific wheel rim drastically alters how inertia feels – a profile built for a 320mm GT rim won’t transfer cleanly to a 290mm formula rim. Download, drive a stint, adjust.

The 360Hz iRacing FFB bug fix

When iRacing rolled out 360Hz native FFB support, Simucube users got incredible detail – and a bug where some setups felt “rubbery”, grainy, or oscillated badly. The fix is mostly firmware-side:

Run TrueDrive 2024.5 or newer – patches the API timing delay between iRacing and the wheelbase.
Ensure the “iRacing 360Hz” mode flag is enabled in TrueDrive’s iRacing-specific profile.
If the wheel still feels grainy, 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 mismatched to actual base output. If you cap TrueDrive at 50%, drop iRacing Wheel Force to match. Set too low = clipping; set too high = lifeless.
Reconstruction Filter at 0 or off. The signal is genuinely too raw on iRacing – you’ll fight the wheel over rough kerbs. 1 is the floor, 3 is the sweet spot.
Running an old TrueDrive on iRacing 360Hz. The pre-2024.5 timing bug is real. Update first, troubleshoot second.
Min Force above 0. Robotic centre rattle. 0% always on Simucube.
Linear Mode unticked. You want raw 1:1 telemetry on DD. Always ticked.
Copying a Paddock profile blind. Use it as a baseline, then tweak. Your wheel rim isn’t the creator’s wheel rim.

Get Reconstruction Filter and Wheel Force right and the rest is small adjustments per car via Auto. The wider iRacing matrix is iRacing FFB settings, the parent is the DD wheel settings hub, and the concept layer is the force feedback explainer. If you’re still shopping for a Simucube, the SC2 lineup is in our direct drive wheel buyer’s guide.

Sources: Daniel Morad TrueDrive Paddock profiles, Dan Suzuki TrueDrive Paddock profiles, Granite Devices community forums, r/iRacing Simucube setup threads.