"Does iRacing support my wheel?" is the wrong question, and it's the one everybody asks. Every DirectInput wheel made in the last twenty years works in iRacing. That was never in doubt. What people are actually asking is whether their base gets the extra layer — the manufacturer API, the 360 Hz update rate, the haptics — and there the answer is genuinely different brand by brand.
I went through iRacing's release notes and pulled every line that mentions a wheel manufacturer's API, 360 Hz mode or wheel haptics. No forum posts, no aggregator lists, no manufacturer marketing. Just what iRacing has published about its own software. What comes out is messier and more useful than any "supported wheels" list I've seen.
Four different things get called "support"
This is where the confusion starts, and it's worth being precise before the table makes sense.
A manufacturer API is a direct software link between iRacing and the base, sitting alongside the normal DirectInput connection. It's the plumbing. On its own it does nothing you can feel.
360 Hz mode is iRacing sending force feedback updates at 360 Hz instead of 60 Hz. That's a steering-torque feature — detail in the wheel, not noise. I've covered what it actually changes in the 360 Hz mode explainer.
Wheel LFE / haptics is a separate channel entirely: engine vibration, kerb texture, wheel slip, sent as tactile buzz. Fanatec calls it FullForce, Logitech calls it TrueForce, iRacing calls the whole family Wheel Low Frequency Effects. That's the WLFE explainer.
An app.ini off-switch is a key you can set to disable the API. Not every brand has one published.
A brand can have the API and neither feature. A brand can have both features. Read the table with that in mind.
What iRacing has actually published
Every line below is from an official release note. Build numbers in brackets.
Simucube — 360 Hz enabled in 2024 Season 2 Patch 1 [2024.03.13.01], with the note "Simucube 360 Hz mode is now enabled" and the requirement that "The latest True Drive (release 2024.3) is required." The API has been refreshed repeatedly since: integrated again in 2024 S3 Patch 3, updated in 2025 S4 Patch 4 [2025.11.18.02], added again in 2026 S1 Initial. 2026 S1 Patch 3 [2026.02.02.02] added "Wheel definitions have been added for Simucube link port devices (v3 wheel bases)." No wheel haptics line anywhere.
Simagic — 360 Hz only, and it took two goes. Disabled in 2024 S3 Patch 3 ("Simagic 360Hz Mode has been disabled," with iRacing adding they would keep testing before public release), then 2024 S3 Patch 4 [2024.08.01.01]: "360 Hz mode is now fully enabled for Simagic wheels. Your wheel needs to be on the latest drivers and firmware." Separately, 2024 S2 Patch 1 records that "Simagic haptic reactor support has been temporarily disabled while we work through some bugs." I found no note re-enabling it in the builds I read. That is not the same as saying it is still off — it means iRacing never published the other half of that story.
Asetek — 360 Hz only. 2025 Season 3 [2024.06.10.01]: "The Asetek API has been updated, which adds support for 360 Hz force feedback."
VRS — 360 Hz only, same build, same wording.
Fanatec — haptics only. Same build: "The Fanatec API has been updated, which adds support for Fanatec's FullForce haptic effects." No 360 Hz line for Fanatec exists in any release note I read. If you have seen "Fanatec has 360 Hz in iRacing" stated as fact, it isn't from iRacing. The API was updated again in 2025 Season 4 to fix a rare lock-up.
MOZA — both. Same build again: "The Moza API has been updated, which adds support for Moza Low Frequency Effects (LFE) Wheel haptic effects and 360 Hz mode." Then a rough patch cycle: 2025 S3 Patch 3 Hotfix 1 [2025.07.02.02] pulled it — "We have temporarily disabled Moza 360 Hz and Wheel LFE effects" over a crash after roughly two hours — and 2025 S3 Patch 4 [2025.07.25.02] restored it: "360Hz and Wheel LFE APIs have been re-enabled."
Thrustmaster — API, no named feature. 2026 S1 Initial [2025.12.08.03]: "The latest Thrustmaster API has been added." 2026 S2 Initial added "Support for the new Thrustmaster wheelbase and wheel rim combo." Neither note claims 360 Hz or haptics.
VNM — the newest entry, and one nobody has written up. 2026 S1 Initial: "The VNM wheel API has been added." Then 2026 S2 Initial [2026.03.09.03]: "The VNM Simulation API has been updated, which fixes a 360 Hz/Wheel LFE mode issue." Worth being careful here: the only evidence VNM gets both features is a bug fix mentioning both. iRacing never announced them when the API landed.
One outlier that isn't a wheel at all: 2024 S3 Patch 4 added "Support for vibrations of Conspit pedals," toggled by the "vibrate pedal and rim" checkbox in the Misc. Options tab. It's the only pedal-side haptic entry in the whole sweep.
Four off-switches, not eight
Here's a detail that gets guides in trouble. iRacing has published exactly four [Force Feedback] API off-switches, all in the same 2025 Season 3 note: loadAsetekAPI=0, loadVRSAPI=0, loadFanatecAPI=0 and loadMozaAPI=0.
There is no published loadSimucubeAPI, no loadSimagicAPI, no loadThrustmasterAPI, no loadVNMAPI. If a settings guide tells you to add one, it is guessing. Simucube does have its own documented key — enable360HzInterpolated=0, named in the 2024 S3 Patch 3 fix line — but that's an interpolation setting, not an API loader.
If you're going into that file, read the app.ini guide first. Copy it before you touch it.
The Logitech gap, stated honestly
Across every build I read, "Logitech" appears exactly once, and only as a comparison — iRacing describing FullForce as "similar to Logitech's TrueForce system."
I am not going to turn that into "Logitech is unsupported," because that would be inventing a conclusion from an absence. TrueForce shipped with the G923 in 2020, well before the window these notes cover, so any Logitech integration would most likely predate them. The honest statement is narrower and still useful: iRacing has published no Logitech API line, no Logitech 360 Hz line and no Logitech off-switch in the modern release notes. If you own a Logitech base and want to know what iRacing is doing with it, there is no official document to point you at. That's a documentation gap on iRacing's side, and it's the second time this year I've hit one — their own controller setup article still routes people to menus that moved in the 2026 Season 3 build.
The 60 Hz fallback nobody talks about
This is the most practically useful line in the whole sweep, and it's buried in 2026 Season 1 Initial. iRacing reduced how many times it tries to connect to the Simucube API, then warned:
"This change may cause older firmware/driver combos to fail to connect and fall back to 60 Hz mode. If you are victim to this, be sure to update to the latest drivers - regardless of state, FFB will continue to work correctly."
Read that again. Your wheel can silently drop out of 360 Hz and keep working perfectly — no error, no warning, just less detail. Which means "my wheel feels a bit flat since the update" is a real diagnosis, not imagination, and the fix is driver and firmware before it is anything in the settings menu.
It also explains why every 360 Hz note that mentions requirements mentions drivers and firmware. Simucube's said True Drive 2024.3. Simagic's said "latest drivers and firmware." The hardware qualifies you; the software actually connects you.
What I'd take from this if I were buying
Not much, and that's the point. None of this is a reason to change base. Motor, encoder and how solidly the thing is mounted decide how a wheel feels — I've made that argument at length in the direct drive explainer and I'll make it again here.
What the table is good for is calibrating expectations. If you buy a Fanatec base expecting 360 Hz because a YouTube comment said so, you'll be hunting a setting that doesn't exist. If you buy MOZA you get both features and a patch history that shows iRacing will pull them when they break things. If you're on Simucube or Simagic you get the steering-detail half and no haptics, which is a perfectly good place to be.
And whatever you own: update the driver, update the firmware, then go and set the thing up properly. The iRacing FFB settings guide will do more for your lap time than any of this will.
As of today the newest published build is 2026 Season 3 Patch 3 Hotfix 2 [2026.07.17.01]. Season 4 release notes are not out yet — when they land, this page gets checked against them.
FAQ
Does iRacing support my wheel?
Almost certainly yes, in the sense that it will work. Any DirectInput wheel drives in iRacing. The manufacturer APIs above are an extra layer on top for a specific set of brands, and not having one costs you feature detail, not function.
Which wheels get 360 Hz in iRacing?
Per iRacing's own release notes: Simucube, Simagic, Asetek, VRS and MOZA. VNM appears via a bug-fix line referencing 360 Hz. Fanatec is not listed anywhere as having it.
Does Fanatec have 360 Hz mode in iRacing?
No release note says so. Fanatec's 2025 Season 3 entry adds FullForce haptics only, while the Asetek, VRS and MOZA entries in that same build explicitly say 360 Hz. Four brands, one release, different capabilities — that contrast is the clearest evidence available.
Why is there no Logitech entry?
iRacing has not published one in these builds. TrueForce predates this release-note window, so absence of a note is not proof of absence of support. There is simply no official documentation to cite.
Can I turn a manufacturer API off?
For four brands, yes: loadAsetekAPI=0, loadVRSAPI=0, loadFanatecAPI=0, loadMozaAPI=0, all under [Force Feedback] in app.ini. No published switch exists for the others.
My wheel felt different after an update — what changed?
Two candidates worth checking before you touch a slider. One, you may have dropped to 60 Hz because your driver or firmware is behind. Two, if it's a buzzing or volume change rather than a steering change, it's the haptics layer, and iRacing applies different default haptics volumes per brand.
Is any of this worth changing wheel base for?
No. It is worth updating software for, and worth knowing about before you buy so you're not chasing a feature your base was never given.