Home

irFFB

irFFB was created to experiment with the 360 Hz telemetry data that was recently made available by iRacing. The original intent was to feed the 360 Hz steering column torque data to a FFB steering wheel so that we could examine what benefits a higher FFB sample rate might bring.

The standard iRacing FFB output writes samples to your wheel 60 times per second, which is arguably not fast enough to generate an accurate (or pleasant) feel at the wheel. This is particularly noticeable with 'Direct Drive' wheels that output higher torques and have lower response times than gear or belt-driven equivalents. The 360 Hz data available in live telemetry provides a significantly smoother signal at the wheel and conveys detail that is absent from the standard 60 Hz output.

The disadvantage of using data from telemetry instead of the standard iRacing FFB is that there is a small delay ( ~ 15 ms) between when the standard FFB is updated and when the data becomes available in telemetry. In addition, since the 360 Hz data is actually written to telemetry 60 times per second (with 6 values each time), irFFB must delay the samples by another 14 ms before sending them to the wheel. This means that the 360 Hz FFB is subject to around 29 ms of total delay referenced to the standard (60 Hz) FFB.

As an alternative, irFFB's 'direct' modes apply low-latency processing to the standard iRacing FFB to improve smoothness and feel but without the latency associated with the 360 Hz data.

irFFB can also modify the FFB (whether based on telemetry or a 'direct' mode) via a number of telemetry-driven effects.

A guide to getting up and running is available in the Configuration page. There are answers to some FAQ at FAQ and the FFB types available are described in the FFB types page. If you're an iRacing member (which you presumably are!) there's a long thread that follows the early irFFB development here and a more recent thread about irFFB 1.3.x here.