We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
wiki: logi-ffb sets the hidraw path itself for DirectInput sims
wiki: clarify force-feedback-vs-TrueForce split and make SDK setup GUI-first The old 'nothing to do' heading let readers stop before the TrueForce setup; now it says force feedback is done but TrueForce is a separate opt-in. The SDK-folder step leads with the app's Setup box; the --sdk-dir flag is presented as the command-line alternative, not a GUI option.
wiki: mark newly-supported games' Simulated TrueForce as available BeamNG.drive, EA F1 (22-25) and EA Sports WRC now have working telemetry parsers in logi-tf-sim, so their Simulated TrueForce moves from planned to available with the per-game setup step.
docs(wiki): add a plain-English force feedback vs TrueForce explainer Force-Feedback-in-Games.md gets a short explainer near the top: force feedback is the physical force you always get with no setup, TrueForce is Logitech's extra vibration and texture layer that some games build in and a background helper can simulate for the rest. Home.md references it and Simulated-TrueForce.md mirrors it briefly so users meet the distinction wherever it matters.
docs(wiki): plain-English rewrite + expanded game compatibility table Rewrite Force Feedback in Games in end-user language and replace the small compat table with a 28-title table (Game / Runs on Linux / Force feedback / Native TrueForce / Simulated TrueForce / What to do), with a verified vs expected key and notes for starred, anti-cheat-blocked and console-only titles. Built from the project compatibility dataset.
User section: installation, games, configuration, simulated TrueForce, troubleshooting, buttons