Repository navigation
Configuring the Wheel
Everything G HUB configures on Windows, this project configures on Linux: rotation range, force-feedback strength and filters, TrueForce level, LIGHTSYNC LEDs, onboard profiles, and per-pedal, steering and handbrake response curves. (A response curve maps how far you move a control to what the game sees.)
Most people do all of this from logi-wheel-gui, the desktop app, so this page leads with it. If you prefer the command line, or run a headless box (no desktop), the terminal app (logi-wheel) has the same feature set. It is covered in Prefer the command line? below, along with the raw sysfs files underneath. (sysfs is the kernel's settings file tree.)
Both apps find the wheel automatically and edit settings live. The packaged
udev rule already makes the settings writable for your desktop user. (udev
is the service that sets device permissions.) There is no group to join. If
writes are refused, that rule is missing. ./tools/setup.sh doctor says so.
Both apps show only what your wheel actually has. Settings, views and actions the hardware does not support are hidden, not shown greyed out. On a G923 that leaves a much smaller surface: rotation range, gain, autocenter and combined pedals, plus its own wheel image and button labels on Info / Testing. LIGHTSYNC, response curves, onboard profile slots and the desktop/onboard mode toggle are direct-drive features. They do not appear; see G923. Desktop profiles work on every wheel, including ones with no onboard slots.
Both apps show gain and autocenter as a percentage, because 0 to 65535 is not a useful thing to type. The sysfs files keep their raw scale. So Oversteer and any script you have already written are unaffected.
Open logi-wheel-gui from your applications menu. It starts on Info / Testing, so the first thing you see is the wheel it found. Every wheel setting is on one page, grouped by category, with live values read from the wheel. Change a value and it applies to the wheel straight away. This is the whole workflow: open the app and click through the pages. No terminal is needed. Views longer than the window scroll, and a scrollbar shows it.

Highlights:
-
G HUB-style curve editor for the pedal, steering and handbrake response curves. Drag control points, set deadzones (the range at each end of a control that is ignored), watch the composed curve, then upload it.

-
LIGHTSYNC editor with per-slot colors (HSV picker), effect, brightness and animation direction. Changes apply to the wheel immediately.
-
Texture group among the settings: the kernel TrueForce texture merge and its feel knobs, cylinder count included.
-
Rev lights read as live state, not as a slider. The strip belongs to whatever feeds it. During a game with the texture merge, that is
logi-rpm-bridge. Otherwise it islogi-tf-sim, fed from telemetry (the game's live data). Both write the strip up to 60 times a second. An editable row was a third writer racing them. The one that lost looked like a broken control. So the row now shows the level, the way its neighbours show live values. This is about who owns the strip, not about what the hardware accepts. The wheel still takes a level. A script canechoone intowheel_rev_level. A deliberate LED test asking for one specific pattern still lands. It goes through a path that validates the value and gates on wheel mode, exactly as a normal write does. -
The screen (RS50 and G PRO): the small display on the base can show something other than the wheel's own menu. On the LIGHTSYNC page, the Screen card says what it is showing now. "Choose what to show..." opens a preview and a list of ready-made screens: gear and speed, a big speed, a rev bar, a rev bar with gear and speed, a four-row race board, a throttle and brake readout, throttle and brake gauges, two static messages and blank. Pick one and it fills the preview, with sample values where a field comes from the game. Show now puts it on the screen. Use during games makes it the dashboard the simulated-TrueForce helper shows while a game runs (see Simulated TrueForce). Give the wheel its menu back does that. You can change the design behind any preset: a layout by name, and one box per field with what fits beside it. The placeholders
{gear},{speed},{speed_mph},{rpm},{rpm_pct},{throttle_pct}and{brake_pct}fill a field from the game. A field wider than its layout allows is refused with a reason, before anything is sent. The G923 has no screen, so the card does not appear for it. -
Info / Testing, the page the app opens on: the wheel's name, serial and firmware in one copyable block; a live input tester (a rotating wheel diagram, button and pedal readouts), so you can answer "does this button reach the computer?"; and the two self-tests described below.

-
Setup is where you turn on the game feel. There are three distinct things here. It helps to keep them straight:
- Force feedback (always on): the physical force through the wheel. It works in every game with no setup. There is nothing to switch on here.
- Built-in TrueForce (some games): Logitech's extra vibration and texture layer, for games that ship it. Setup lists the sims it finds across Steam (Proton and native builds), Lutris and Heroic. (Proton is Steam's layer for running Windows games.) It installs or removes Logitech's TrueForce files per game, with a folder picker for those files. If you have a racing sim it does not recognise, use the Add a game button. It lets you pick the game from your detected games, or point at its Wine prefix (the folder where Wine keeps a game's Windows files). Then it sets that game up too.
- Simulated TrueForce (the background helper, for the rest): for games with no built-in TrueForce, the helper builds that texture from the game's live data. Setup has its master switch and per-game switches.
Each game's card carries the one launch line to paste into Steam. It says what the wrapper will do for that game on the wheel you have attached. Where the driver blends the engine note in, it also says whether that game's SDK forwarder is staged yet, and which rev-light style the strip uses (a full bar, or the car's own dashboard band). The card also says when something other than you writes a setting. So a read-only row reads as informative, not broken.
See Force Feedback in Games for the plain-English explainer, and Simulated TrueForce for the helper in detail.

-
Profiles: on a wheel with onboard slots, onboard mode shows its five named slots. You can rename them, and there is a Back button. Desktop mode manages computer-side presets. You can save (a dedicated Save button), apply and delete them. A wheel with no onboard slots gets the desktop presets only.
The RS Shifter & Handbrake, the RS H-Shifter and the Logitech Racing Adapter plug into the accessory ports on the wheel base. Both apps show the Shifter & Handbrake's settings while it is attached. They hide them again when it is unplugged.
The Shifter & Handbrake has a three-position switch on its base. The app reads that switch and greys out whatever does not apply. In analog handbrake mode the handbrake curve is live, and the two trigger points are not.
The H-Shifter's seven gates and reverse report as buttons 12 to 20. Button 19 is not used. The driver turns on the base's routing for it in desktop mode, so the gates also work outside a game. The Info / Testing page shows which gate is in. If you plug the shifter straight into the computer by USB instead, the page reads it there too. It shows that next to the gate.
The Racing Adapter takes a G29, G920 or G923 pedal set and a DB9 Driving Force Shifter. On the base, the driver turns on the routing for it in desktop mode, like the H-Shifter. The Info / Testing page also reads the adapter and the Shifter & Handbrake on their own USB cables.
Plug in two wheels and both apps manage both. The window puts a button for
each next to the title. The terminal app switches with w. Everything
follows the pick: the settings you see, the values you write, the live
input monitor and the tests all belong to the wheel currently selected. The
name in the header says which one that is. Wheels of the same model are
numbered, so you can tell them apart.
Nothing is shared between them. Each wheel keeps its own settings on its own hardware. Switching does not copy anything across.
Simulated TrueForce is the one thing that still needs telling. It drives
one wheel. Left on auto, it takes a G923 whenever it finds one. So on a
rig with a G923 and a direct-drive wheel, the direct-drive wheel never gets
it. The Setup page has a wheel picker for that. See
Simulated TrueForce.
Info / Testing carries two guarded tests, in both apps: a force-feedback sequence and a TrueForce texture sequence. Each shows its whole plan up front. Then it walks the steps one at a time, with a countdown before each step and a state next to it (pending, running, done, skipped). So nothing moves before you know what it is about to do.
The force sequence covers: constant force in both directions; a rising ramp; spring, damper, friction and inertia; the sine, square, triangle and sawtooth waveforms; an envelope fade in and out; two effects playing at once; and gain and autocenter demos. Anything your wheel's engine does not advertise is marked skipped, not run. On a G923 that is friction. The texture sequence is four rising steps on the TrueForce channel, from a slow, heavy rumble to a fine, high-frequency buzz.
Both ask for your consent first, and you can cancel at any point. Hold the rim first. On a direct-drive wheel these are real forces.
If you run headless, live in an SSH session, or just prefer a terminal, the rest of this page is for you. The terminal app logi-wheel has the same feature set as the desktop app. Everything both apps set is also a plain sysfs file you can script directly (see Sysfs API Reference). Desktop-app users can stop here.
The TUI (the terminal user interface) is a sidebar of views plus a content pane. The number keys jump straight to a view. It starts on Info / Testing, naming the wheel it found. Values are typed and validated before they reach the wheel. So an out-of-range value is rejected in the UI, instead of erroring at the device. A view taller than the terminal scrolls, and a scrollbar shows it.

On a wheel with a desktop / onboard split, settings that only apply in one
mode are flagged. The app can switch between the two with the d key. A
write that needs the other mode tells you so, instead of failing silently.
A wheel without that split (the G923) has no mode toggle at all.
Press ? at any time for the complete key list of the current context.
The in-app overlay and the footer render from the same table, so they are
the authoritative reference.

Global (whenever no text entry is open)
| Key | Action |
|---|---|
| 1 to 7 | Jump straight to that sidebar view |
| Tab | Switch focus between the sidebar and the content pane |
| Esc | Close the topmost editor / overlay, else back to the sidebar |
| ? | The full key list for the current context |
| w | Switch to the next wheel (only with more than one attached) |
| q | Quit |
Settings views (content focus):
- Up/Down select a setting.
- Enter edits it, or runs an action.
-
iexplains the selected setting. -
atoggles sensitivity / full curve for an axis. -
dtoggles desktop / onboard mode. -
rre-reads all values from the wheel.
Editing a value: Left/Right nudge the value (or type, for text fields). Enter commits. Esc cancels.
Opens on any curve setting (steering, per-pedal, handbrake). Up/Down move
between fields (point, input, output, lower deadzone, upper deadzone).
Left/Right adjust. +/- add or delete a point. Enter uploads the curve:

The LIGHTSYNC view composes each custom slot: colors per LED, effect, brightness, animation direction. The strip preview mirrors what the wheel shows. Changes apply live:

The color picker paints individual LEDs from a palette or hex entry. Tab
switches between the strip and the palette. Enter paints the selected LED.
a paints all. p paints the LED and its mirror pair (for the symmetric
directions). x opens hex entry. w writes the strip to the wheel:

On an RS50 or G PRO, press Enter on the Screen row of the LIGHTSYNC view.
That opens the screen editor: a preview of the base's display beside a
list of ready-made screens. Up and Down pick one, and the preview follows.
Enter shows it on the screen now. g makes it the simulated-TrueForce
dashboard for games. x hands the screen back to the wheel's own menu. Tab
opens the design behind the preset for changes: Left and Right pick a
layout, Up and Down move between its fields, and typing fills them. The
same placeholders as the window's editor fill a field from the game.
The startup view: wheel name, serial, firmware, app and driver versions
(copyable with c, handy for bug reports), a live input monitor, and the
self-tests. f runs the force-feedback sequence, and
t runs the TrueForce texture one. Both ask for your consent first:

The Setup view manages the game helpers: logi-ffb hints, per-game install and removal of Logitech's TrueForce files across your detected Proton games, the folder those files live in, a game compatibility table, and the simulated-TrueForce helper controls:

Everything the apps set is also available as plain sysfs attributes under
/sys/class/hidraw/hidrawX/device/wheel_*:
H=$(ls -d /sys/class/hidraw/*/device/wheel_range | head -1 | xargs dirname)
echo 0 > "$H/wheel_profile" # desktop mode
echo 900 > "$H/wheel_range" # lock-to-lock degrees
echo 65 > "$H/wheel_strength" # overall FFB strength, percentThe GUI tool Oversteer also
recognizes many of them, through the driver's compatibility aliases. On a
G923 the attributes use the classic names (range, gain, autocenter,
combine_pedals) instead of wheel_*. The complete attribute reference is
the Sysfs API Reference.