G923

G923

The belt-driven G923 gets its own feature set from this driver, separate from the direct-drive RS50 / G PRO path: it speaks a different classic protocol, so its force feedback, settings and game setup all differ. This page collects everything G923-specific.

The one rule to remember: launch-option advice elsewhere on this wiki (in particular PROTON_ENABLE_HIDRAW=1) is for the direct-drive wheels only. On a G923 it kills force feedback and enables nothing. The G923 recipe is: no launch options, Steam Input off.

Which G923 do you have?

Two editions, with different USB IDs and support levels:

Edition	USB IDs	Status
PlayStation	046d:c267 at boot, 046d:c266 after the driver's automatic PC-mode switch	✅ verified on hardware
Xbox	046d:c26d at boot, 046d:c26e after the automatic PC-mode switch	🟡 needs a tester

The G920 and G29 are not covered by this project; they keep working with the in-tree kernel drivers, unchanged.

PlayStation edition: what works

• Full classic force feedback: constant, spring, damper, friction, inertia, periodic and ramp effects plus autocenter, driven by a classic force-feedback engine ported from berarma's new-lg4ff. The wheel boots as c267 and the driver switches it to PC mode (c266) automatically.
• Settings under the classic sysfs names (Oversteer-compatible, not the wheel_* names the direct-drive wheels use): range (40-900 degrees), gain, autocenter, combine_pedals, plus a read-only ffb_output showing the live force. Details in the Sysfs API Reference.
• Rev LEDs as standard Linux LEDs: five /sys/class/leds entries (::RPM1 to ::RPM5), one per mirrored pair of the 10-LED strip, usable by any LED-aware tool.
• Simulated TrueForce through logi-tf-sim (next section).
• logi-dd and logi-dd-gui recognise the wheel and expose its four settings, with its own wheel image on the Info / Testing page.

Hardware-verified on a real c266: constant force and autocenter feel correct in Assetto Corsa Competizione, and the LED sweep.

In games: no launch options

Force feedback works out of the box in native and Proton games; the wheel is a standard Linux force-feedback wheel. Per game:

1. Leave Launch Options empty. Do not set PROTON_ENABLE_HIDRAW (that recipe is for the RS50 / G PRO and breaks the G923's force feedback).
2. Properties, Controller: set Disable Steam Input for the game.

That is the whole setup. The logi-ffb proxy is not needed either; it exists for the direct-drive wheels' hidraw path.

TrueForce: simulated, not native

Logitech's own SDK TrueForce path does not work for the PlayStation G923 on Linux: the SDK DLL delegates the actual haptics to G HUB, which Proton does not provide. Skip the TrueForce file install for this wheel; it buys nothing.

Instead, the G923 speaks the same TrueForce stream protocol as the RS50 and G PRO on its third USB interface, which the driver exposes for userspace. logi-tf-sim streams the same telemetry-driven engine haptics to it, while mirroring the wheel's live force-feedback output (ffb_output) into the stream so force feedback and TrueForce agree instead of fighting. Hardware-confirmed as vibration; feel reports under real game telemetry are welcome. Setup is the same as for the other wheels: Simulated TrueForce.

Xbox edition

The Xbox G923 (046d:c26e in PC mode) routes force feedback through the same HID++ path as the G920. It boots into a console-only mode (046d:c26d) with no input node at all; installing usb_modeswitch (a recommended, not required, package) lets a udev rule switch it into PC mode automatically on plug-in. If it never switches, the out-of-tree xone driver may have claimed the device first.

This edition is unverified: if you own one, a working / not-working report is the top thing the project needs. See Troubleshooting for how to report.

Driver coexistence

A PID-scoped udev rule (installed by the packages and by setup.sh) reclaims c266/c267/c26e from a competing driver that wins the initial bind race; every other Logitech device stays on its usual driver. The one exception is berarma's new-lg4ff (hid-logitech-new), blacklisted outright since it otherwise races this driver for c266/c267; a wheel you ran on it (G29, G27, DFGT, ...) falls back to the in-tree hid-logitech instead.