The more powerful the steering wheel is, the lower the strength you'll need to choose here. A good starting point is:[list][*]Entry level wheels configured to 1-3Nm: use 350 to 500[*]Mid range wheels configured to 3-5Nm: use 200 to 350[*]High end wheels configured to 5-30Nm: use 50 to 200[/list]If the chosen strength is too high, the most subtle details may become more noticeable, but the medium and strong details will max out and blend together, losing useful feedback. This is called [i]clipping[/i], and it happens because the steering wheel is being asked for more torque than it can produce.[br][br]You can check for clipping with the UI apps '{{'ui.apps.steering_position.name'|translate}}' and '{{'ui.apps.ffb_graph.name'|translate}}'. We recommend you reduce the strength until clipping happens rarely (or happens only in situations where you don't mind the lack of detail).[br][br]Note: force feedback in certain vehicles could be weaker or stronger than average (such as mods that weren't tested with a steering wheel). You can tune those vehicles individually through {{'ui.dashboard.vehicleconfig'|translate}} > {{'ui.vehicleconfig.tuning'|translate}} > Setup-specific force feedback multiplier.
Can be used to reduce larger vibrations in the steering wheel (lower frequency oscillations).[br][br]Abusing this setting will compromise the amount of detail and responsiveness you can feel through the steering wheel, so tweak with care.[br][br][b]If in doubt, use '{{'ui.controls.ffb.smoothing2automatic'|translate}}' instead.[/b]
How often the physics engine is allowed to send force feedback updates to the steering wheel:[list][*]High values improve detail, but a value too high can severely impact your framerate or increase ffb lag.[*]A value too low (such as 30Hz) won't feel smooth.[*]'{{'ui.controls.ffb.updateRateLimit.automatic'|translate}}' will guess the fastest usable rate, by running a quick analysis each time you use the steering wheel. [b]If in doubt, use this.[/b][/list][i]'{{'ui.controls.ffb.updateRateLimit.automatic'|translate}}' is not perfect: in very rare cases you may need to manually choose an even lower rate to avoid performance issues.[/i][br][br]Note: the real update rate depends on several factors and external limitations; this option merely imposes an upper limit.
Allows to choose between two internal methods of sending the force feedback requests:[list][*]'[i]{{'ui.controls.ffb.updateType.fast'|translate}}[/i]': [b]if in doubt, use this[/b].[*]'[i]{{'ui.controls.ffb.updateType.slow'|translate}}[/i]': this slow alternative can reduce the framerate. It should only be used as a workaround for some rare buggy steering wheels.[/list]If your steering wheel works better when using '[i]{{'ui.controls.ffb.updateType.slow'|translate}}[/i]', please search for firmware and driver updates. If the issue persists, contact our support team.
Allows to customize how the steering wheel will respond to various torque requests.[br][br]For example, increasing response of lower torques and decreasing response of higher torques, compensating for a non-linear response, etc.[br][br][b]Please check the Steering Wheel Setup documentation page for details.[/b][br][br]Quick guide: once this setting is enabled and applied, place a curve file in your [code]settings/inputmaps/[/code] directory, press <code>ctrl+L</code>, click <code>Apply</code> and reopen this menu. The inputmap <code>.diff</code> file will be automatically updated with the new curve data.[br][br]Accepted filenames:[list][*]wheel.csv (universal format, each line having a <code>force</code>,<code>response</code> pair of values; header lines are ignored, and any numeric scale can be used, as it will be automatically normalized and sanitized)[*]wheel.lut (compatible with Assetto Corsa™<code>ff_post_process</code> curves)[*]wheel.log (compatible with iRacing™ WheelCheck csv files using <code>log-2</code> option)[*]wheel.fcm (compatible with Project Cars™ Force Curve Modifier exported files using <code>linear force response</code> option)[/list]
