Invalid or damaged force-feedback settings

An unreadable ACC force-feedback configuration can prevent the expected wheel response.

Approval requiredActiveEvidence reviewed 2026-09-03Guide updated 2026-09-29

Checks and expected results

Before you repair it

Check for an explicit FFB/settings-file failure and note the current gain and other wheel settings.
Close Assetto Corsa Competizione and preserve ffbUserSettings.json before removing its active copy.
Note the settings you will need to re-enter and change only the identified file or files.

How to confirm the result

Relaunch Assetto Corsa Competizione, review the rebuilt settings, and repeat the original action. Confirm that force feedback works during a cautious test using reviewed settings. If it does not help, keep the new evidence and use the backup to restore the previous configuration with the simulator closed.

Repair limits and when to stop

Review force levels before driving. This does not diagnose every loss of wheel force or alter wheelbase firmware.

How PitMedic recognizes it

ACC log evidence identifies FFB or ffbUserSettings.json as failed, invalid, or unreadable.

Signals PitMedic may recognize

ffbUserSettings.json
FFB
force feedback

Built-in response

Preserve ffbUserSettings.json and remove only the active copy so ACC can regenerate force-feedback settings.

Repair safetySignificant / reversible / ask first

Verification sources

PitMedic prioritizes vendor documentation and labels community findings separately.

ACC v1.6 update notesKunos Simulazioni · Official source
Kunos documents that per-car force-feedback values are stored in ffbUserSettings.json.
Open source