Skip to content

History / Wheel Force Feedback

Revisions

  • Docs-audit fixes across the 3.4 pages Five-lens audit against the code: - Wheel: RPM-LED telemetry reads the SCS plugin, not OutGauge. Add the OutGauge games (BeamNG.drive, Live for Speed). Thrustmaster friction renders as damper (same 0x07 as inertia). Drop the "only" framing on the periodic generator. - Remote Link: gamepad-only is off by default (the pair-dialog checkbox starts unchecked), not "unknown peers start limited". Secure identity is DPAPI machine scope, not "this Windows account". - Home: lightbar count thirteen -> fifteen. Macro fire modes four -> five. Remote Link nav framed as many PCs. - Lighting: "thirteen base modes" -> "thirteen base entries" (Off plus twelve), consistent with the fifteen-mode intro. - Controller Audio: tab scope is per pad per slot. - Wheel Force Feedback dev page: ReEvaluate -> TickFfb (no ReEvaluate exists). "8-byte logical report" -> vendor-shaped command (Thrustmaster pads to 64/32).

    @hifihedgehog hifihedgehog committed Jun 15, 2026
  • Add 3.4 developer-reference pages and cross-links New internals pages for Remote Link, Controller Audio, Wheel force feedback, and MIDI input, each grounded in the live source (classes, files, data flow). Link them from the Home developer-reference index. Add the MIDI enumeration phase and the vendor-wheel force-feedback branch to Input Pipeline, the new persisted fields to Settings and Serialization, and the engine-side subsystems note to Services Layer. Also small prose fixes to the user pages: drop a defensive "not input-only" phrasing on Remote Link, fix a link alias on Wheel, Americanize a spelling on MIDI Input.

    @hifihedgehog hifihedgehog committed Jun 15, 2026