From e370ac6cd19453090b136c39fd52903761a7ba09 Mon Sep 17 00:00:00 2001 From: mescon <5875228+mescon@users.noreply.github.com> Date: Tue, 22 Sep 2026 12:53:41 +0200 Subject: [PATCH] docs(games): the proven DiRT Rally 2.0 proxy recipe, and purpleferret's full credit DiRT Rally 2.0 works end to end through the logi-ffb proxy on a G PRO under Proton, confirmed by a reporter (#105): the proxy turned on for the game, the telemetry at extradata=3 for the engine note, and a device_defines.xml line giving the stand-in wheel an id the game keys its force feedback on. The registry setup text and the wiki now carry the exact steps instead of calling the route untested. purpleferret's credit is expanded to the whole DirectInput route they drove: the four faults their logs found and the debug trace that proved the game sent the wheel nothing until it had an identity the game knew. --- CHANGELOG.md | 12 ++++++++++++ CREDITS.md | 12 +++++++++--- .../logi-wheel/crates/logi-wheel-core/src/games.rs | 2 +- 3 files changed, 22 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 6de3489..251310b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,18 @@ changes to the sysfs surface, minor versions add supported wheels or new attributes, patch versions are bug fixes and documentation. Pre-1.0 the contract is "it works on RS50 and G Pro as listed here". +## Unreleased + +**The DiRT Rally 2.0 recipe is written down, end to end.** With the proxy +turned on (`690790 ffb=proxy`), the telemetry set to `extradata="3"`, and a +one-line `device_defines.xml` entry that gives the stand-in wheel an +identity the game knows, a G PRO gets force feedback, the rev LEDs and the +wheel-base display in that game under Proton, confirmed by a reporter +([#105](../../issues/105)). The exact steps are in the registry setup text +and on the wiki. The game keys force feedback on the wheel's USB id and the +stand-in's was new to it, which is why it sent nothing until told; a +built-in way to present a known identity is a candidate for later. + ## 0.42.3 - 2026-09-22 **The launcher says when the running module is older than the apps, and diff --git a/CREDITS.md b/CREDITS.md index 6bdddb9..4d15338 100644 --- a/CREDITS.md +++ b/CREDITS.md @@ -95,9 +95,15 @@ until the last round. [#87](../../issues/87)). Those numbers are what the engine's condition forces will be calibrated against, and his wedge report on the Xbox edition found a detector that reset itself on every error reply. -- **[purpleferret](https://github.com/purpleferret)** - a G PRO with no - force feedback in Assetto Corsa Rally, with the launcher log that showed - the game had been listed on the wrong route ([#105](../../issues/105)). +- **[purpleferret](https://github.com/purpleferret)** - a G PRO through + the whole DirectInput proxy route on DiRT Rally 2.0 + ([#105](../../issues/105)): the report that put Assetto Corsa Rally on + the right route, then a run of precise logs and USB captures that found + four faults nothing here could have shown (the proxy never aimed at the + wheel, its errors going nowhere a Steam user can read, `/dev/uhid` + root-only where uhid is not loaded, and a shifter's gears dropped for + want of buttons past 32), and finally the debug trace proving the game + sent the wheel nothing until it was given an identity the game knew. - **[Lorenzoo78](https://github.com/Lorenzoo78)** - the Assetto Corsa EVO stutter report under the launcher ([#74](../../issues/74)). - **[matthiasvegh](https://github.com/matthiasvegh)** - twelve issues and diff --git a/userspace/logi-wheel/crates/logi-wheel-core/src/games.rs b/userspace/logi-wheel/crates/logi-wheel-core/src/games.rs index 5332e9c..499dbe0 100644 --- a/userspace/logi-wheel/crates/logi-wheel-core/src/games.rs +++ b/userspace/logi-wheel/crates/logi-wheel-core/src/games.rs @@ -787,7 +787,7 @@ logi-tf-sim.", ffb: Ffb::NativeEvdev, native_trueforce: Support::Expected, simulated_tf: SimTf::LiveNow("dirt-rally-2"), - setup: "Switch on the game's UDP telemetry, which is off by default: in `hardware_settings_config.xml` (under the game's documents folder in the prefix) set `` (the daemon needs the `extradata=\"3\"` packet; the default 0 is too short to synthesise from), port 20777 as it ships; launch options `logi-launch %command%` (it starts logi-tf-sim for you); Steam Input off. Force feedback under Proton reaches this game only through Wine's joystick path, which on some builds does not present the wheel at all (#105); the `logi-ffb` proxy route is under test there.", + setup: "Switch on the game's UDP telemetry, which is off by default: in `hardware_settings_config.xml` (under the game's documents folder in the prefix) set `` (the daemon needs the `extradata=\"3\"` packet; the default 0 is too short to synthesise from), port 20777 as it ships; launch options `logi-launch %command%` (it starts logi-tf-sim for you); Steam Input off. Force feedback under Proton reaches this game only through Wine's joystick path, which on some builds does not present the wheel at all; where it does not, the `logi-ffb` proxy route works, confirmed on a G PRO: add `690790 ffb=proxy` to `~/.config/logi-wheel/games.conf`, and because the game keys force feedback on the wheel's USB id, add a `device_defines.xml` line for the virtual wheel (the exact line is on the wiki, Force Feedback in Games) (#105).", confidence: Confidence::Documented, }, GameCompat {