Skip to content
mescon edited this page Nov 6, 2026 · 18 revisions

G923

The gear-driven G923 gets its own feature set from this driver. It is separate from the direct-drive RS50 / G PRO path. (A direct-drive wheel's motor turns the rim directly; the G923 uses gears.) The G923 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: PROTON_ENABLE_HIDRAW=1 is for the direct-drive wheels only. On a G923 it kills force feedback and enables nothing. Never copy it from someone else's post.

Use logi-launch %command% and the question does not arise. It works out the recipe from the wheel you have plugged in. On a G923 it never sets that variable.

Which G923 do you have?

There are two editions. They have 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 ✅ force feedback and TrueForce verified by an owner; rev lights implemented, awaiting confirmation in a game

The G920 and G29 are not covered by this project. They keep working with the in-tree kernel drivers, unchanged. (In-tree means the drivers that ship inside the Linux kernel itself.)

PlayStation edition: what works

  • Full classic force feedback: constant, spring, damper, friction, inertia, periodic and ramp effects, plus autocenter. A classic force-feedback engine drives them. It was ported from berarma's new-lg4ff. The wheel boots as c267. The driver switches it to PC mode (c266) automatically.

  • Settings under the classic sysfs names. (sysfs is the kernel's file tree for device settings, under /sys.) The names are Oversteer-compatible, not the wheel_* names the direct-drive wheels use. (Oversteer is the community wheel-settings app.) They are range (40 to 900 degrees), gain, autocenter, combine_pedals, plus a read-only ffb_output that shows the live force. Details are in the Sysfs API Reference.

  • Pedals the right way round. This wheel sends all three pedals inverted: 255 with the pedal released and 0 with it flat to the floor. Nothing in HID marks an axis as inverted. (HID is the USB standard for input devices.) So every layer passes that on unchanged. Left alone, a game reads every pedal as fully applied at rest. The driver turns them the right way up. A released pedal then reads 0, like every other Linux input device. Raw HID is left exactly as the wheel sent it. A Wine or Proton game that reads the wheel that way expects the Windows convention. (Proton is Steam's layer for running Windows games. Wine is the software underneath it.) Have you already inverted these axes inside your games? Then clear that setting, or set the g923_pedal_invert module parameter to N.

  • Rev LEDs as standard Linux LEDs: five /sys/class/leds entries (::RPM1 to ::RPM5). Each entry is one mirrored pair of the 10-LED strip. Any LED-aware tool can use them. logi-tf-sim drives them from a game's live telemetry (the live data a game publishes about the car). That is the same RPM display the direct-drive wheels get. They fill outside in, ::RPM1 first.

    The packaged udev rule covers their brightness files, so a normal user can drive them. (udev is the Linux service that sets device permissions.) Does the strip stay dark after an upgrade? Reload the udev rules. sudo ./tools/setup.sh does it.

  • Simulated TrueForce through logi-tf-sim (next section). TrueForce is Logitech's fine, fast vibration layer on top of normal force feedback.

  • logi-wheel and logi-wheel-gui recognise the wheel and show its four settings. They show the wheel's own image on the Info / Testing page, and its own button labels. The labels are the 18 real buttons of a PlayStation G923, captured from the hardware. The RS50 callout diagram is not shown for this wheel.

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

Simulated TrueForce is verified end to end on the same wheel, in Assetto Corsa Competizione and EVO. The test: the car stands still in the pit box with the engine revving. Force feedback cannot produce anything there, so what you feel came from telemetry. The rev strip fills 0 to 5 and drains back. That was read from the brightness files, not judged by eye.

In the settings app

The apps show a G923 only what it has. So LIGHTSYNC, the response-curve editors, the onboard profile slots and the desktop / onboard mode toggle are absent, not greyed out. (LIGHTSYNC is Logitech's LED colour feature.) Desktop profiles do work here, despite the wheel having no onboard slots. (Desktop profiles are computer-side presets you save and apply.) Gain and autocenter appear as percentages in the app. The sysfs files keep their raw 0 to 65535 scale, so Oversteer and scripts are unaffected.

The force-feedback self-test on Info / Testing runs the full sequence. It marks friction skipped: the classic engine advertises every effect except FF_FRICTION. See Configuring the Wheel.

(The app is logi-wheel. logi-dd is kept as a symlink. This wheel is why the app is not called that any more: see Installation.)

In games

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

  1. Open Launch Options and enter logi-launch %command%.
  2. Open Properties, Controller. Set Disable Steam Input for the game.

That is the whole setup. It is the same line as on every other wheel. What it does behind that line is not the same, and that is the point of using it. On a G923 it never sets PROTON_ENABLE_HIDRAW. It starts the simulated TrueForce daemon (a background helper). A direct-drive wheel does not want that daemon, because it has the game's own TrueForce.

By hand instead: leave Launch Options empty for most sims. Plain force feedback needs nothing there. The exception is DirectInput sims (Le Mans Ultimate, rFactor 2, iRacing, RaceRoom). DirectInput is the older Windows force-feedback interface. Even there, the one line is logi-launch %command%, on a G923 just as on a direct-drive wheel. The launcher runs the logi-ffb proxy for you. Whether a game needs that proxy depends on how it asks for force feedback, not on which wheel is plugged in.

TrueForce: simulated, not native

Logitech's own SDK TrueForce path does not work for the PlayStation G923 on Linux. (The SDK is Logitech's TrueForce software library.) The SDK DLL hands the actual haptics to G HUB, Logitech's Windows software. Proton does not provide G HUB. 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. The driver exposes that interface for userspace (programs that run outside the kernel). logi-tf-sim streams the same telemetry-driven engine haptics to it. It also mirrors 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. (HID++ is Logitech's command protocol on top of HID.) It boots into a console-only mode (046d:c26d) with no input node at all. Install usb_modeswitch (a recommended, not required, package). A udev rule then switches the wheel into PC mode automatically on plug-in. Does it never switch? Then the out-of-tree xone driver may have claimed the device first.

Force feedback and TrueForce are both confirmed on a real unit. An owner confirmed them over the course of issue #27. Neither existed for this wheel on Linux before.

Rev lights

Two separate problems kept this strip dark. Both are now fixed.

The display starts switched off. 0x807A fn2 reports which effect the strip is showing. This wheel answers 0 for "nothing". In that state it refuses every level with an internal error. So a completely correct command looked ignored. Sending fn3 with effect 2 starts the display. After that, the same level is accepted. The driver reads the state at probe (the moment it first attaches to the wheel). It sends that call only for a wheel reporting 0, never for one already showing something.

Nothing registered any LED device for it. This edition reaches neither the direct-drive path nor the classic path. The direct-drive path exposes wheel_rev_level. The classic path registers the LED classdevs, and its device table lists c266 and c267 but not c26e. So even with the protocol right, there was nothing for a telemetry feeder to write to. It now exposes the same five ::RPM1..RPM5 entries the PlayStation edition does. So logi-tf-sim, Oversteer and any LED-aware tool work with no change.

The strip follows RPM in a game. An owner confirmed this in Assetto Corsa EVO on the force engine route below (issue #72, 2026-09-07). It needs a telemetry feed like any rev strip. So it lights only in games logi-tf-sim can read. The driver logs what it found at probe:

logitech-dd 0003:046D:C26E.0007: G923 (Xbox): rev strip: 0x807A at index 0x12, 5 LEDs, display off (will be switched on)

Do your rev lights not follow RPM? Then that line (or its absence) in dmesg is the first thing to report.

The force engine route

Two owners independently found the same setup in September 2026 (issues #72 and #84): the driver's own force engine, g923_xbox_dd_engine=1, with raw HID left off (PROTON_ENABLE_HIDRAW unset). On the stock HID++ 0x8123 path, force feedback and TrueForce are mutually exclusive on this wheel. The firmware sums the effects where the driver cannot see them. On the engine, they arrive together. Measured on a real unit: all four condition effects (spring, damper, friction, inertia) are alive, and the rev strip follows revs when fed.

To turn it on, run these two commands. The first writes the option. The second reloads the module:

echo 'options hid-logitech-dd g923_xbox_dd_engine=1' | sudo tee /etc/modprobe.d/logitech-trueforce.conf
sudo modprobe -r hid-logitech-dd && sudo modprobe hid-logitech-dd

Set the rotation range in the app. A game may show 1080 through Logitech's SDK. That is its guess and changes nothing. Release 0.40.1 changed four things. The engine now reads and sets the real range and strength through the wheel's classic feature. It scales its force by the strength slider. It switches the wheel's own centring spring off at load. It stops the motor whine from the wheel's 2 ms position reports. The route is still opt-in and marked experimental. A faint residue of that whine is being worked on in issue #85. Findings for this route are collected in issue #87.

Is Logitech's own SDK library in the game's prefix? (The prefix is the private Windows-style folder Proton keeps for each game.) Then the launcher takes this wheel down the same route as a direct-drive wheel. This holds since the release from 0.41.0. That route is: raw HID scoped to it, a dinput8 proxy that answers the SDK's rotation question, and the simulated daemon for the rev lights and screen only. The game's own force and TrueForce, engine note included, reach the wheel. The range set in the app moves it. Assetto Corsa EVO's own steering-lock setting sends nothing on this route, so it stays inert here. (On Windows it goes through G HUB.) Proven with the SDK files from a G HUB install (issue #91). Whether the copies the app's Setup page installs stream on this edition is still to be confirmed by an owner.

Driver coexistence

A PID-scoped udev rule reclaims c266/c267/c26e from a competing driver that wins the initial bind race. (A PID is the USB product id.) The packages and setup.sh install the rule. Every other Logitech device stays on its usual driver. The one exception is berarma's new-lg4ff (hid-logitech-new). It is 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.

Clone this wiki locally