Skip to content

games: name the DiRT Rally 2.0 telemetry switch, record what the AC Rally capture showed - #117

Merged
mescon merged 3 commits into
masterfrom
docs/registry-notes
Sep 21, 2026
Merged

mescon merged 3 commits into
masterfrom
docs/registry-notes

Conversation

@mescon

@mescon mescon commented Sep 21, 2026

Copy link
Copy Markdown
Owner

Registry text only (the generated setup document's cells are unaffected). DiRT Rally 2.0 now names hardware_settings_config.xml and the udp enabled attribute; AC Rally records the G PRO capture result from #105. Based on #116 to keep the branch chain linear.

The virtual wheel exposed 32 buttons and dropped the kernel's codes for
buttons 17 to 21 (BTN_TRIGGER_HAPPY to +4) as unused, because the RS50
never emits them. A G PRO with a shifter does, and its higher gears
could not be bound in DiRT Rally 2.0 (#105). The input report now
carries 64 buttons. The layout keeps every bit the RS50's DirectInput
users have already bound: the joystick range on bits 0-15, the RS50's
extended block on 16-31 as before, the five recovered buttons on 32-36,
and anything past the RS50 block's sixteen codes from 37 on; a code
past 64 is dropped, not wrapped.

The proxy's report-level trace (LOGI_FFB_DEBUG) went to stderr only,
which under Steam is a console nobody reads; it now goes through the
same log mirror as the proxy's other messages, so one opted-in run
shows whether the game sends any force at all.
…ardown, no false module failure

Four small things found while working #105, none needing a reporter:

The launcher's first log line showed "module v0.41.0, logi-tf-sim
0.42.0" through a day of tests before anyone read it as what it was: a
package update had installed the new module but the kernel kept running
the old one, because a plugged-in wheel keeps it busy. The launcher now
says that in words, with the reload command.

A session that ran as a child of the launcher only because it had to
start the daemon itself (no user service manager) also got the TrueForce
teardown pair at exit. That pair is for sessions that could have left the
wheel's engine started: raw HID, the texture merge, the bridge, an
in-prefix helper. It is now sent only for those.

The doctor failed the kernel-module check whenever no wheel was attached,
although the module binds on plug-in and a bare desk is the machine doing
what it should. It now warns in that case and fails only when a wheel is
on the bus and the module still is not loaded.

logi-wheel --launch-plan printed "wheel=none" and stopped when no wheel
was attached, even with a class named by --wheel. It now prints the plan
for the named class, with a note, so the recipe can be read and tested
without a wheel; a raw-HID scope still needs the attached wheel.

Also the one shellcheck finding the launcher carried (SC1087).
…ally capture showed

DiRT Rally 2.0's setup line said to enable UDP telemetry; it now names
the file and the attribute, since the engine note was reported missing
by someone who had not found the switch (#105), and notes that force
feedback under Proton depends on Wine's joystick path presenting the
wheel, which some builds do not. AC Rally's line records that on a G PRO
a USB capture showed Logitech's library loading and sending the wheel
nothing: the route is in place, the game does not drive it.
@mescon
mescon enabled auto-merge September 21, 2026 22:28
@sonarqubecloud

Copy link
Copy Markdown

@mescon
mescon merged commit b840ed9 into master Sep 21, 2026
23 checks passed
@mescon
mescon deleted the docs/registry-notes branch September 22, 2026 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant