If your wheel started buzzing after an iRacing update and nobody could tell you why, this is almost certainly the answer. iRacing has been quietly rolling out a 360Hz force feedback path to one manufacturer at a time since March 2024, it arrives switched on by default, and there is no single page anywhere that tells you who has it and what it does.

I have been driving on it since it landed on my base, and I have also spent an evening reading every iRacing release note that mentions it, because the forum version of this story is mostly wrong. Here is what the official notes actually say.

What 360Hz mode actually is

Standard force feedback on a PC goes out over DirectInput. That pipe runs at 60Hz — sixty force updates per second. iRacing's physics engine runs far faster than that internally, so for two decades the sim has been calculating detail it had no way to send you. That gap is the entire reason irFFB existed.

360Hz mode replaces the DirectInput pipe with a direct API connection between iRacing and the wheelbase manufacturer's own driver. Instead of one force value sixty times a second, the sim hands over a much denser stream and the base reconstructs it. Six times the update rate, same physics underneath.

What you feel is not "more force". It is texture that was previously being averaged away — the small stuff between the big stuff. Kerb strike edges are sharper. Front tyre scrub arrives earlier in the slide. On a low-grip surface the wheel stops feeling like it is reporting events and starts feeling like it is reporting a surface.

It is worth being precise about what it is not. It does not change the physics, the tyre model, or how much peak torque your base produces. If you are chasing a stronger wheel, this is the wrong lever — that is what your base's intensity and torque limit settings are for, and I go through those properly in the MOZA Pit House settings guide.

The timeline, from iRacing's own release notes

This matters because manufacturers keep announcing it as if it were new, and their dates do not always match iRacing's.

2024 Season 2 Patch 1 (build 2024.03.13.01) is where it first appears in an official note: "Simucube 360 Hz mode is now enabled." The note adds that the latest True Drive, release 2024.3, is required. Simucube was the launch partner.

2024 Season 3 Patch 3 (2024.07.12.02) is the honest one. "Simagic 360Hz Mode has been disabled," with iRacing adding that they would "continue to test and debug to ensure it's working appropriately before release to the public." The same patch fixed a bug where force feedback was not being properly enabled when Simucube users set enable360HzInterpolated=0.

2024 Season 3 Patch 4 (2024.08.01.01) brought Simagic back: "360 Hz mode is now fully enabled for Simagic wheels. Your wheel needs to be on the latest drivers and firmware."

2025 Season 3 (release build, notes modified 10 June 2025) is the big one, and its headline says so — "We have also added support for 360 Hz Force Feedback for several more devices!" In the Controls section:

  • The Asetek API was updated to add 360Hz. Off switch: [Force Feedback] loadAsetekAPI=0.
  • The VRS API was updated to add 360Hz. Off switch: loadVRSAPI=0.
  • The Moza API was updated "which adds support for Moza Low Frequency Effects (LFE) Wheel haptic effects and 360 Hz mode." Off switch: loadMozaAPI=0.
  • The Fanatec API was updated for FullForce — which iRacing describes as part of its Wheel Low Frequency Effects system and "similar to Logitech's TrueForce system." Note carefully: that entry is about haptics, not 360Hz.

That last distinction gets mangled constantly. In iRacing's own notes, Fanatec received FullForce haptics in that release, not 360Hz force feedback. If you are on a Fanatec base and someone tells you to enable 360Hz mode, ask them where they read it. My Fanatec iRacing FFB settings page is a better use of your evening.

2026 Season 3 (2026.06.09.01, season live 16 June 2026) added a dedicated Force Feedback and Haptics page in the sim's Settings. iRacing's note says all the advanced FFB and haptics settings moved there, with basic FFB functions left duplicated on the Driving page, and the tab labels were later shortened to Haptics and FFB. If you last went looking for these controls a year ago, they have moved.

MOZA: what the support article says, and what it does not

MOZA is the case worth going through properly, partly because it is the newest addition and partly because its own documentation is the only place the buzzing complaint gets addressed at all.

MOZA's iRacing support article opens its FAQ with the exact question people are typing into Google: why does my wheelbase vibrate at a high frequency and make abnormal noises after the iRacing update? The answer is that "iRacing 6.10 updated version supports 360hz and Wheel LFE effects for MOZA devices."

The requirements MOZA publishes are specific:

  • Base firmware version 1.2.5.5 or higher
  • Pit House version 1.3.1.50 or higher
  • All MOZA bases support 360Hz and Wheel LFE

And the line that catches everyone: "The game automatically enables both features by default. You can manually disable them if preferred."

So the buzz is not a fault. It is Wheel LFE — engine vibration, drivetrain, rev limiter — being played through your wheel because iRacing turned it on for you. Whether you like it is a taste question. Whether your base makes an unpleasant noise doing it is a hardware question, and on smaller bases the answer is sometimes yes.

Two things MOZA's article does not tell you. First, "iRacing 6.10" is MOZA's version naming, not iRacing's — iRacing versions builds by date, and the change belongs to the 2025 Season 3 release. Second, MOZA's own R9 V3 product page dates the feature to a May iRacing update; the release notes put it in the June build. Trust the release notes.

How to turn it off

Both features are separate switches, and you almost certainly want to try turning off one before the other.

Wheel LFE first. This is the vibration. MOZA's article says it can be reduced or disabled directly in iRacing's in-game settings interface — as of 2026 Season 3 that means the Force Feedback and Haptics page. For finer control, open Documents\iRacing\app.ini, find the [TrueForce] section, and adjust the per-effect gains in decibels. MOZA publishes the defaults, and they are not all zero: engine RPM sits at -9 dB, gear change at +3 dB, rumble strip at -3 dB, wheel slip at +6 dB, with car body acceleration, drive shaft, rev limit and road texture at 0. Drop volTrueForcePhysEngineRPM_dB further before you touch anything else — engine drone is the usual culprit.

360Hz second, and only if you still have a problem. In Documents\iRacing\app.ini, search for the 360Hz interpolation entry and set it to 0. Here is a real trap: the key name is not consistent across official sources. MOZA's article names it enableFFB360HzInterpolated, while iRacing's own 2024 Season 3 Patch 3 note refers to enable360HzInterpolated for Simucube. I am not going to pretend I know which one your build ships with. Search app.ini for "360Hz" and edit whatever you find — with the sim closed, or it will overwrite you on exit.

Failing that, every manufacturer has a load<Brand>API=0 switch in the [Force Feedback] section, which cuts the direct API connection entirely and drops you back to plain DirectInput. That is the blunt instrument. It kills the haptics too.

Should you leave it on?

Yes, for almost everybody. I run it on.

The honest caveat is that 360Hz will expose a base that was already oscillating or already too noisy. It is not creating the problem — it is delivering more of a signal your hardware was previously smoothing over for you. If your wheel gets twitchy on the straights after enabling it, the fix is damping and inertia on the base side, not switching the mode off. I cover that balance in the MOZA R9 FFB settings guide, and the same logic transfers to any direct drive base.

There is also a decent argument that the update makes your in-sim FFB strength worth rechecking. More texture through the same output range means more chance of clipping the peaks. Run WheelCheck again and set your per-car strength properly rather than guessing — the process is the same one in my iRacing wheel and FFB settings guide.

One last thing worth saying, because it saves people money: none of this is a reason to buy a new base. Every MOZA base supports it according to MOZA, Simucube has had it since 2024, and the feature is a driver-level connection rather than a hardware capability. If you are shopping, the things that actually differ between bases are motor and encoder — I go through that in the four-brand comparison and in what NexGen actually changes.

FAQ

What is 360Hz mode in iRacing?

It is a direct API connection between iRacing and your wheelbase driver that replaces the 60Hz DirectInput force feedback pipe with a roughly six-times-denser stream. Same physics, more of the detail the sim was already calculating.

Which wheels support iRacing 360Hz?

From iRacing's own release notes: Simucube (2024 Season 2 Patch 1), Simagic (fully enabled 2024 Season 3 Patch 4), and Asetek, VRS and MOZA (2025 Season 3). Fanatec's entry in that same release was FullForce haptics, not 360Hz.

Why does my wheel buzz or make noise after an iRacing update?

That is almost certainly Wheel LFE, not 360Hz. MOZA's own support article names this as the top FAQ and confirms iRacing enables both features automatically by default. Turn LFE down in the sim's Force Feedback and Haptics page first.

Do I need to turn 360Hz on manually?

No. iRacing enables it by default where it is supported. What you may need is current firmware and driver software — MOZA specifies base firmware 1.2.5.5 or higher and Pit House 1.3.1.50 or higher, and Simucube's original enablement required True Drive 2024.3.

Does 360Hz mode make you faster?

Not directly. It gives you earlier warning of the front tyre letting go, which over a stint is worth something. Nobody has ever found a tenth in a checkbox.

Is 360Hz the same as Logitech TrueForce or Fanatec FullForce?

No. Those are haptic systems that send high-frequency vibration to the rim — iRacing groups them under Wheel Low Frequency Effects and describes FullForce as similar to TrueForce. 360Hz mode is about the rate of the main force feedback signal. MOZA's implementation happens to add both at once, which is why they get confused.