Repository navigation
Home
This project is a Linux kernel driver plus userspace tools for three Logitech racing wheels: the direct-drive RS50, the direct-drive G PRO Racing Wheel, and the gear-driven G923 (both editions). A kernel driver is the part of Linux that talks to the hardware. Userspace tools are the normal programs that run on top of it.
It brings these features to Linux, including in Proton and Wine games. (Proton is Steam's layer for running Windows games. Wine is the same idea outside Steam.)
- Force feedback.
- TrueForce haptics. They are built in where a game supports them. For titles without them, a simulated version is built from the game's live data.
- A live RPM rev-light display.
- The base's screen as a dashboard.
- LIGHTSYNC LED control.
- The same wheel settings G HUB gives you on Windows.
You manage all of it from a desktop app (logi-wheel-gui) or a terminal app (logi-wheel). Several wheels plugged in at once are each managed separately.

Four steps, whichever of these wheels you own.
1. Install it. On Arch and its relatives, run paru -S logi-wheel-gui.
For every other distribution, see Installation.
2. Plug the wheel in and open Logi Wheel. The app finds the wheel. It shows every setting that wheel supports. For a tour, see Configuring the Wheel.
3. Set your games up from its Setup page. The page lists the sims it found across Steam, Lutris and Heroic. Each game has its own buttons:
- Install relay puts the telemetry relay into that game's Proton folder. Telemetry is the live data a game sends out, such as RPM and speed. The relay feeds simulated TrueForce and the rev lights in sims that keep their telemetry in shared memory (the Assetto Corsa family, iRacing, RaceRoom, rFactor 2, Le Mans Ultimate).
- Install TrueForce files puts Logitech's own TrueForce files into that game's Proton folder. Use it for sims with TrueForce built in, on a direct-drive wheel. It needs the one-time copy below. A G923 skips this step. That wheel does not answer Logitech's SDK (the software kit games use to talk to the wheel), so it gets TrueForce from the simulated helper instead.
The one-time copy: Logitech's TrueForce files. These files cannot be redistributed. You supply them from a Windows G HUB installation. Copy the whole
Logifolder to~/.local/share/logitech-trueforce/sdk. Keep its layout. You should end up with.../sdk/Logi/Trueforce/<version>/trueforce_sdk_x64.dlland.../sdk/Logi/wheel_sdk/<version>/logi_steering_wheel_x64.dll. The version numbers your G HUB shipped are the right ones. The Setup page's TrueForce files section shows the folder it reads, and whether it found the files. Full detail: Force Feedback in Games.
4. Put one launch option on each sim. In Steam, open Properties, then General, then Launch Options. Enter:
logi-launch %command%
This line is the same for every game and every wheel. For most people it
is the only setup step. logi-launch works out what this game needs on the
wheel you have plugged in, then does it:
- force feedback for older DirectInput sims (DirectInput is the older Windows method for input and force feedback);
- the game's own TrueForce, where the game supports it;
- engine texture and live rev lights from the game's own telemetry in AC EVO;
- simulated TrueForce and rev lights everywhere else.
It also tears everything down when the game exits. With two wheels
attached, it settles on one of them. --wheel dd or --wheel g923 says
which. Everything it starts goes to that wheel, so a game on one wheel
cannot disturb a session on the other. The Setup page shows what it will do
for each of your games. That differs by wheel. Details in
Force Feedback in Games.
One thing it cannot do for you: turn Steam Input off for the game. Open Properties, then Controller, then choose "Disable Steam Input". If Steam Input stays on, it hides the wheel behind a virtual gamepad. Force feedback then never arrives.
Run this in a terminal. It lists the Logitech devices on USB:
lsusb | grep -i 046d| Product id | Wheel | Notes |
|---|---|---|
c275, c276
|
RS50 (both editions) | The development hardware. Everything is verified on it. The Xbox edition plugs in as c275. It is switched to c276 automatically, which needs usb_modeswitch installed. |
c272 |
RS50 in compatibility mode, or a G PRO (Xbox/PC) | The two share this id. Logi Wheel names which one it found. |
c268 |
G PRO Racing Wheel (PS/PC) | Same code path as the RS50. |
c266, c267
|
G923 PlayStation edition | No other Linux driver gives this wheel force feedback at all. See G923. |
c26d, c26e
|
G923 Xbox edition | Needs usb_modeswitch installed. See G923. |
A wheel that plugs in as c267, c26d or c275 is switched to its PC
mode automatically. So a different id after plugging in is expected, not a
fault. On a system without systemd, sudo logi-wheel-modeswitch does the
switch by hand.
If nothing above matches, this driver is not for your wheel. The in-tree
hid-logitech-hidppdriver already serves the G920. (In-tree means the driver ships with the Linux kernel itself.) The in-treehid-logitech-hidppandhid-lg4ffdrivers serve the older G25/G27/G29.
The RS50 is the development hardware, so it is verified directly. The G PRO runs the same code path, so it is expected to work. A few G PRO items still wait for an owner's confirmation.
Legend: ✅ verified on hardware · 🟢 shares the verified code path, expected to work · 🟡 needs a tester
| Capability | RS50 | G PRO |
|---|---|---|
| Steering, pedals, buttons, D-pad | ✅ | 🟢 |
| Force feedback (works like a normal Linux wheel, full effect suite) | ✅ | 🟢 |
Force feedback in DirectInput games (the older force-feedback method, via logi-ffb) |
🟡 | 🟡 |
| TrueForce haptics (Proton, using Logitech's TrueForce files) | ✅ | 🟢 |
| AC EVO engine texture + rev lights from the game's own telemetry (kernel merge + bridge) | ✅ | 🟢 |
| Rotation range (90 to 2700°), strength, damping, filters | ✅ | 🟢 |
| Pedal response curves, sensitivity, deadzones, combined pedals | ✅ | 🟢 |
| RS Shifter & Handbrake (shift, digital + analog handbrake) | ✅ | 🟢 |
| RS H-Shifter (7 gates + reverse, works on the desktop, hot-plug) | ✅ | 🟢 |
| Racing Adapter on the base (legacy pedal sets + DB9 shifter, hot-plug) | ✅ | 🟢 |
| LIGHTSYNC RGB LEDs (slots, colors, direction; edits apply live) | ✅ (faceplate strip) | 🟡 (rev lights) |
| RPM rev-light display (level fill, center-out) | ✅ | 🟡 |
| The base's screen: presets, your own text, a dashboard fed by the game | ✅ (RS50, G PRO) | no screen |
Simulated TrueForce from a game's live data (logi-tf-sim) |
✅ (sweep-verified) | 🟢 |
| Centre calibration, mode / profile switching, computer-side profiles | ✅ | 🟢 |
The table above covers the direct-drive pair. The gear-driven G923 speaks an older Logitech protocol. So it takes a different path inside the driver, with its own feature set: full classic force feedback (hardware-verified on both editions), rev lights, and simulated TrueForce. It has its own page: G923.
Its in-game setup is no longer different. logi-launch resolves the recipe
per wheel. So the same launch option is right on a G923 and on an RS50,
even though what it does behind them is opposite. That matters more on this
wheel than on any other. PROTON_ENABLE_HIDRAW=1 is a setting a
direct-drive wheel needs for TrueForce. On a G923 it removes force
feedback. Copying that setting from someone else's post is the most common
way to break a G923.
Start here if you own one of these wheels and want it working. Most people
want the desktop app. Install logi-wheel-gui (it pulls in everything) and
do the rest from the app. You need the terminal for one install command
only.
New here? In plain English: force feedback is the physical force you feel through the wheel (the weight of the car, kerbs, impacts). It works with no setup. TrueForce is Logitech's extra layer of fine, fast vibration and texture on top. Some games build it in. For the rest, a background helper can simulate it. Full explainer in Force Feedback in Games.
- Installation: the desktop app (recommended), plus per-distro packages, from source and atomic distros.
- Force Feedback in Games: force feedback vs TrueForce explained, out of the box, in Proton, the TrueForce setup, and DirectInput games.
- Configuring the Wheel: a tour of logi-wheel-gui and the logi-wheel terminal app.
- Simulated TrueForce: engine haptics and rev lights for games without native TrueForce.
- G923: everything specific to the gear-driven G923 (both editions).
- Add a Game: capture a game's telemetry to help add simulated TrueForce support for it.
- Troubleshooting: symptoms, fixes, and how to report a bug.
- Button Reference: which button index is which physical control.
Start here if you want to understand or extend the stack:
- Architecture: how the kernel driver and the userspace pieces fit together.
-
Sysfs API Reference: every
wheel_*attribute. - Protocol Specification: the USB and HID++ protocol, with sub-pages for Protocol Force Feedback and Protocol LIGHTSYNC.
- TrueForce Protocol: the audio-haptic stream format.
- libtrueforce: the native C implementation of the TrueForce SDK.
- logi-ffb: the DirectInput force-feedback proxy.
- Simulated TrueForce Internals: telemetry parsers, synthesis, rev LEDs.
- Building and Contributing: building, testing, and contributing captures.
The kernel driver and tooling are GPL-2.0-only. libtrueforce is LGPL-2.1-or-later, so native Linux apps may link it. Logitech's TrueForce files are not part of this project and are not redistributed. You supply them from your own Windows G HUB installation.