docs: record native-mode TrueForce verification (compat no longer required)

SDK-driven game TrueForce under Proton was packet-confirmed on the RS50
in native mode (046d:c276) driving AC EVO on 2026-07-08: Wine's HID
backend opened interface 2 on the native PID and the SDK streamed ~2 kHz
of type-0x01 packets (239k OUT / 120s) on ep 0x03, and it was felt. This
disproves the earlier assumption that the SDK requires the G PRO compat
PID (c272).

Update every place that stated or implied compat mode is required for
TrueForce: the two setup recipes (README + GETTING_STARTED) now mark the
compat-mode switch optional with native as the verified default, the
protocol doc and sdk README record both modes verified, the udev comment
drops the "borrows the PID so the SDK accepts it" rationale, and the
README "State of the driver" stamp moves to v0.11.0 / 2026-07-08.

Author: mescon

CHANGELOG.md

@@ -10,7 +10,11 @@ the contract is "it works on RS50 and G Pro as listed here".
 35 commits since the `v0.10.0` tag on 2026-07-03. The TrueForce force
 path was reworked from TF4ALL protocol findings and feel-verified on
 RS50 hardware (clean texture route, host-alive force unaffected by
-texture playback, response-curve upload/reset confirmed).
+texture playback, response-curve upload/reset confirmed). SDK-driven
+game TrueForce under Proton was additionally packet-confirmed in the
+RS50's **native mode** (`046d:c276`, AC EVO, ~2 kHz type-0x01 stream on
+ep 0x03), so native mode no longer trades away game TrueForce for its
+full 2700 range.
 
 ### TrueForce stream reworked from TF4ALL cross-pollination
 

README.md

@@ -117,10 +117,12 @@ owner to validate · - not applicable.
 | Centre calibration | ✅ | 🟢 |
 | Mode / profile switching | ✅ | 🟢 |
 
-The RS50 is the development hardware, so its column is verified directly.
-A real G PRO runs the **same `hidpp_dd_ff_*` code path** as an RS50 in G PRO
-compatibility mode (which *is* verified), so it is expected to work; we
-just do not have one to confirm against. **G920 / G923** keep working as
+The RS50 is the development hardware, so its column is verified directly
+in both native (`046d:c276`) and G PRO compatibility (`046d:c272`) modes,
+including SDK game TrueForce under Proton in each. A real G PRO runs the
+**same `hidpp_dd_ff_*` code path** as an RS50 in G PRO compatibility mode,
+so it is expected to work; we just do not have one to confirm against.
+**G920 / G923** keep working as
 a drop-in through the inherited upstream HID++ `0x8123` FFB path; the
 RS50/G-PRO-specific `wheel_*` settings do not apply to them. The **G923**
 speaks the same TrueForce stream protocol as the DD wheels (confirmed on
@@ -178,14 +180,17 @@ All effects are routed to the wheel's single direct-drive motor
 >   after the driver was reloaded while Steam ran: **restart Steam
 >   fully** - its device list goes stale across driver reloads.
 
-### State of the driver (v0.10.0, 2026-07-03)
+### State of the driver (v0.11.0, 2026-07-08)
 
 An honest calibration of what "supported" means today:
 
-**Verified on hardware** (one RS50, G PRO compatibility mode, plus
-extensive USB-capture cross-checks): everything marked with a check in
-the matrix above, including full-lap gameplay in ACC and AC EVO with
-simultaneous steering FFB and TrueForce.
+**Verified on hardware** (one RS50, in **both** G PRO compatibility and
+native `046d:c276` modes, plus extensive USB-capture cross-checks):
+everything marked with a check in the matrix above, including full-lap
+gameplay in ACC and AC EVO with simultaneous steering FFB and TrueForce.
+SDK-driven TrueForce under Proton is now packet-confirmed in native mode
+as well (AC EVO, 2026-07-08), so native mode gets the full 2700 range
+without giving up game TrueForce.
 
 **Expected but awaiting independent confirmation:**
 - A **real G PRO Racing Wheel** runs the identical code path and
@@ -404,13 +409,19 @@ signed SDK DLLs running unmodified under Proton. The same recipe is
 expected to work for the other Logitech-SDK-aware sims (Le Mans
 Ultimate, AMS2, Assetto Corsa, rFactor 2, iRacing). The recipe
 applies to both the RS50 and the G PRO Racing
-Wheel for Xbox/PC. Step 1 is RS50-only.
-
-1. **(RS50 only)** Switch the wheel into "G PRO compatibility" mode
-   via the OLED menu. The wheel reboots and reappears as
-   `046d:c272`, which is the PID ACC's TrueForce check accepts.
-2. Set the wheel's steering angle. The compat-mode factory default
-   is 90°, much too small to drive with. Two equivalent paths:
+Wheel for Xbox/PC. Step 1 is RS50-only and optional.
+
+1. **(RS50, optional)** You can switch the wheel into "G PRO
+   compatibility" mode via the OLED menu (it reboots and reappears as
+   `046d:c272`), but as of 2026-07-08 this is not required: the SDK
+   also accepts the RS50's **native** PID `046d:c276`, verified
+   end-to-end in AC EVO (usbmon-confirmed TrueForce stream). Native
+   mode additionally unlocks the full 2700 range. Use compat mode only
+   as a fallback if a specific game's SDK build does not recognise the
+   native PID.
+2. Set the wheel's steering angle. The default range can be very small
+   (compat mode's factory default is 90°), much too small to drive
+   with. Two equivalent paths:
    - **From Linux (recommended)**: enter desktop mode and set the
      range live via sysfs:
      ```bash

docs/GETTING_STARTED.md

@@ -118,8 +118,14 @@ For each sim, in Steam:
    this game, so the game sees the wheel directly instead of a
    virtual gamepad.
 
-**(RS50 only)** switch the wheel into "G PRO compatibility" mode via
-its OLED menu first - the SDK's device check accepts that identity.
+**(RS50, optional)** you can switch the wheel into "G PRO compatibility"
+mode via its OLED menu, but as of 2026-07-08 this is no longer required:
+the SDK also accepts the RS50's **native** identity (`046d:c276`), verified
+end-to-end in AC EVO (usbmon-confirmed TrueForce stream). Native mode
+additionally unlocks the full 2700 range. Compat mode remains a safe
+fallback if a particular game's SDK build does not recognise the native
+PID; if TrueForce does not engage in native, try compat and please open
+an issue noting the game.
 
 ## 4. Set your steering range, then race
 

docs/TRUEFORCE_PROTOCOL.md

@@ -2,7 +2,7 @@
 
 > **Status**: the kernel driver leaves interface 2's hidraw node open for userspace. Two userspace paths consume that node:
 >
-> - **Proton sims (verified working)**: `tools/install-tf-shim.sh` copies Logitech's own Authenticode-signed SDK DLLs (`trueforce_sdk_x64.dll`, `logi_steering_wheel_x64.dll`) into each Wine prefix and registers the CLSIDs. The unmodified DLLs run inside Wine and write to the wheel via Wine's HID stack, which reaches our kernel driver. No shim, no IAT hooks, no certificate spoofing. End-to-end verified against **Assetto Corsa Competizione** and **Assetto Corsa EVO** on RS50 in G PRO compatibility mode (both 2026-04-26 / 2026-04-29).
+> - **Proton sims (verified working)**: `tools/install-tf-shim.sh` copies Logitech's own Authenticode-signed SDK DLLs (`trueforce_sdk_x64.dll`, `logi_steering_wheel_x64.dll`) into each Wine prefix and registers the CLSIDs. The unmodified DLLs run inside Wine and write to the wheel via Wine's HID stack, which reaches our kernel driver. No shim, no IAT hooks, no certificate spoofing. End-to-end verified against **Assetto Corsa Competizione** and **Assetto Corsa EVO** under Proton on RS50 in **both modes**: G PRO compatibility mode (`046d:c272`, 2026-04-26 / 2026-04-29) and **native mode** (`046d:c276`, AC EVO, 2026-07-08). The native run was usbmon-confirmed: Wine's HID backend opened interface 2 on the native PID and the SDK streamed ~2 kHz of type-0x01 packets (239k OUT over ~120 s) on ep 0x03. The SDK DLLs open and drive the wheel identically at either PID, so compat mode is not required for TrueForce.
 > - **Native Linux apps**: `userspace/libtrueforce/` is a native C reimplementation of the same protocol described below. Useful for Linux apps that want to drive TrueForce directly (telemetry-driven haptic generators, custom test rigs, etc.).
 >
 > Originally reverse-engineered from [issue #5](https://github.com/mescon/logitech-trueforce-linux-driver/issues/5) captures (BeamNG.drive + G Pro, contributed by [@SandSeppel](https://github.com/SandSeppel)) and re-verified 2026-04-21 against an RS50 + ACC capture on the same host. The two wheels use byte-for-byte identical init and streaming packets.

sdk/README.md

@@ -105,7 +105,7 @@ Both channels coexist at runtime: the SDK sets both KF (slow, steering feel) and
 
 ### How we use this in practice
 
-- The Proton recipe in the project README installs the unmodified, Logitech-signed Trueforce DLL into each Wine prefix and registers its CLSID. The DLL talks to Wine's HID stack rather than the (nonexistent on Linux) G HUB Agent named pipe; Wine's HID stack reaches our kernel driver. End-to-end verified against ACC. See `tools/install-tf-shim.sh`.
+- The Proton recipe in the project README installs the unmodified, Logitech-signed Trueforce DLL into each Wine prefix and registers its CLSID. The DLL talks to Wine's HID stack rather than the (nonexistent on Linux) G HUB Agent named pipe; Wine's HID stack reaches our kernel driver. End-to-end verified against ACC and AC EVO, on RS50 in both G PRO compatibility mode and native mode (`046d:c276`, AC EVO 2026-07-08, usbmon-confirmed). See `tools/install-tf-shim.sh`.
 - For native Linux apps that want to drive Trueforce directly (no Wine in the loop), `userspace/libtrueforce/` is a from-scratch C reimplementation of the same protocol; `include/trueforce.h` mirrors the 62 named exports of the Windows DLL.
 - `logiTrueForceSetStreamTF` suggested a bulk-upload path in addition to per-sample. libtrueforce supports streaming writes via `write(2)` on the wheel's interface-2 hidraw node rather than a single ioctl per sample, matching the wire-level format.
 

udev/70-logitech-trueforce.rules

@@ -16,9 +16,10 @@
 #   Direct-drive TrueForce wheels (this driver's primary targets):
 #     C276  RS50 Direct Drive - NATIVE mode (full sysfs surface)
 #     C272  G PRO Racing Wheel (Xbox/PC) - ALSO the RS50 in G PRO
-#           COMPATIBILITY mode (the RS50 borrows this PID so the SDK's
-#           device check accepts it; the driver tells the two apart by
-#           USB product string)
+#           COMPATIBILITY mode (the RS50 can present this PID; the
+#           driver tells the two apart by USB product string). The SDK
+#           also accepts the RS50's native C276, so compat mode is not
+#           required for TrueForce.
 #     C268  G PRO Racing Wheel (PlayStation/PC)
 #
 #   Gear-driven, but same TrueForce stream protocol - access is purely