wiki: how to capture a game's telemetry to add support
1a43560
wiki: Setup finds sims across Steam, Lutris and Heroic; recapture screenshot
c413898
wiki: recapture the GUI screenshots for the redesigned app
78372b4
wiki: logi-ffb sets the hidraw path itself for DirectInput sims
01f4b2a
wiki: drop the input-group step from the manual install too
The udev rule handles wheel-settings permission for the local user on
every install path, source included.
2b820e6
wiki: no terminal step for the desktop app
The udev rule now makes wheel settings writable for the local user, so
the previous 'one required terminal command' (adding yourself to the
input group) is gone; the recommended path is now just: install the
app, plug in, open it.
ad8a91d
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.
e8de758
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.
25a9317
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.
71e8182
docs(wiki): lead install and config with the desktop-app path
Restructure Installation.md around a "Which do I want" intro, a recommended
desktop-app subsection (logi-dd-gui one-liners plus the single required
input-group step), and a clearly separated manual / command-line subsection
that keeps the packages table, from-source setup.sh, doctor and the
atomic-distro steps verbatim. Configuring-the-Wheel.md now leads with the GUI
walkthrough and files the terminal app and sysfs under a "Prefer the command
line" alternative; the Setup section names force feedback, built-in TrueForce
and simulated TrueForce as three distinct things.
c9b4e24
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.
3c7f573
docs(wiki): rewrite user pages in plain English
Translate developer jargon (SDK, daemon, telemetry, UDP, hidraw, PID
collection, DLLs, evdev, Proton prefix) to plain end-user wording across
Home, Installation, Configuring the Wheel, Simulated TrueForce and
Troubleshooting. Wording pass only: structure, wiki links, images, code
blocks and literal commands unchanged.
ec1d3d6
wiki: crisp terminal-rendered TUI screenshots
Replace the earlier poorly-rendered TUI captures with real terminal
renders (alacritty): settings, LIGHTSYNC, colour picker, Setup, Info /
Testing, help overlay and the curve editor.
4e96c1a
wiki: drop the toolkit name from the user-facing app description
Users do not need to know the GUI is built with Slint; the framework
mention stays on the developer pages (Architecture, Building).
d0d0b40
Developer section: architecture, sysfs, protocol, TrueForce, libtrueforce, logi-ffb, tf-sim internals, contributing
045ef12
User section: installation, games, configuration, simulated TrueForce, troubleshooting, buttons
de9dfbf
Home page and sidebar navigation
f71ea54
Add images: GUI and TUI screenshots, button layout, logo
6cc4f8a