Skip to content

games: DiRT Rally 2.0 setup text carries the device_defines line (#125) #126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mescon merged 1 commit into from
Sep 29, 2026
Merged

games: DiRT Rally 2.0 setup text carries the device_defines line (#125) #126

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,14 @@ 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

**DiRT Rally 2.0's setup text carries the `device_defines.xml` line
itself.** It pointed to the wiki for the exact line, and that wiki page had
been emptied by a bad edit (restored), so an RS50 owner used the wheel's
own id and the game sent no force ([#125](../../issues/125)). The line
names the proxy's virtual wheel, `{C2DD046D-...}`, on every wheel.

## 0.42.4 - 2026-09-24

**The SDK proxy is no longer recommended where it cannot load, and the
Expand Down
2 changes: 1 addition & 1 deletion userspace/logi-wheel/crates/logi-wheel-core/src/games.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -781,7 +781,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 `<udp enabled=\"true\" extradata=\"3\" ...>` (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).",
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 `<udp enabled=\"true\" extradata=\"3\" ...>` (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 `<device id=\"{C2DD046D-0000-0000-0000-504944564944}\" name=\"lg_g29\" priority=\"100\" type=\"wheel\" />` to `input/devices/device_defines.xml` in the game folder: that is the virtual wheel's id on every wheel, not your wheel's own (#105, #125).",
confidence: Confidence::Documented,
},
GameCompat {
Expand Down
Loading