We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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).
Remote Link: frame device sharing as many PCs, not two Remote Link is a many-to-many mesh. LinkServer holds a list of connections, a shared device's input fans out to every consuming peer, and reverse feedback is addressed by the owning peer's fingerprint. Pairing is pairwise (one six-digit code per pair), but a PC can be linked to many others and one shared controller can drive games on several PCs at once. Reword the two-PCs framing across the callout, feature card, screenshot caption, FAQ, setup steps, and requirements.
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.
Frame Remote Link internet play as a VPN capability
Document 3.4 features: Remote Link, Wheel, Controller Audio, MIDI Input New pages for the four 3.4 headline features. Add a 3.4 What's new section and nav links on Home. Cross-link from Force Feedback (native wheel FFB), Devices (MIDI input cards), and Driver Management (MIDI input needs Windows MIDI Services). Audio page states the mirror is a Windows-output loopback, not game-audio packet interception, and that DS4 audio is Bluetooth-only. Remote Link page states local-network-only with no built-in internet path.