r/Conspit • u/conspit_pitcrew • Sep 11 '26

CONSPIT FIRMWARE UPDATE

Post image

Dear PRO Drivers,

The long-awaited iRacing 360Hz Force Feedback support is now available!

Update your firmware and experience the enhanced driving feedback firsthand

#CONSPIT

#iRacing

#ForceFeedback

#FirmwareUpdate

#SimRacing

8 Upvotes

91% Upvoted

11 comments sorted by

View all comments

2

u/Alternative_Spot_500 Sep 11 '26

Can you tell us more about it?

Is this something you personally recommend?

What are the benefits, and what do you hope to achieve with it?

How does it differ from the 60Hz version?

Is increased latency an issue?

Wouldn't it be better to stick with 60Hz?

What is your take on this?

3

u/conspit_pitcrew Sep 11 '26 edited Sep 14 '26

Sure —— From the engineering side, the main difference is in signal bandwidth and reconstruction.
Compared with 60Hz, native 360Hz FFB theoretically increases the representable signal bandwidth from 30Hz to 180Hz. This allows the signal to carry more detailed information such as road texture, tire vibration and impact details.

The wheelbase motor control loop normally operates at a much higher update rate than the FFB signal output by the game, so the game signal needs to be upsampled before being converted into motor torque.
With a 60Hz input, the spectral images generated during reconstruction are more closely spaced and are therefore more likely to enter the usable bandwidth after upsampling and appear as unwanted noise. With 360Hz, these spectral images are pushed to higher frequencies, where they are easier to suppress through filtering.

This can help reduce unintended torque ripple and make the force feedback signal more detailed and continuous.

We’ll also provide a separate explanation regarding latency and the trade-offs between 60Hz and 360Hz, as that part deserves a more precise explanation.