Skip to content

Simulated TrueForce

mescon edited this page Nov 6, 2026 · 20 revisions

Simulated TrueForce

A quick reminder of the difference. Force feedback is the physical force you feel through the wheel (weight, road pull, kerbs). It works with no setup. TrueForce is Logitech's extra layer of fine, fast vibration and texture on top. Some games build it in. This page is about adding it to the games that do not. The full explainer is in Force Feedback in Games.

Normally the game itself provides TrueForce, through Logitech's TrueForce support (see Force Feedback in Games). For titles with no built-in TrueForce, this project ships logi-tf-sim. It is a small background helper. It builds engine haptics from the game's own live data: engine RPM, speed and throttle, sent over the local network. (This live data is called telemetry.) It plays them through the wheel's real TrueForce audio path. The same live data drives the wheel's rev-light strip as a live RPM display.

On the G923 this is the only TrueForce there is. Logitech's own TrueForce files do not work for it on Linux (see G923). So the helper is the supported path. It finds a G923 automatically and streams to the wheel's own TrueForce interface. It mirrors the live force-feedback output into the stream, so haptics and force feedback agree instead of fighting.

What you feel

An engine note through the wheel rim. It is a fundamental tone at the engine's firing rate, plus harmonics. It gets louder with throttle. It is present at idle and silent when the engine is off. The rev LEDs fill with RPM. On the RS50 they use your active LIGHTSYNC slot's colors, drawn center-out. (LIGHTSYNC is Logitech's LED color feature.) On a real G PRO rim, the onboard profile owns the colors. On a G923 the helper drives the five LED pairs of the strip directly. They are also standard Linux LEDs; see G923. On the Xbox edition the LED path is implemented but not yet confirmed in a game.

Supported games

Any game that broadcasts its live data in one of these formats:

Format Default port Games
Codemasters / EA float array 20777 DiRT Rally 2.0, DiRT 4 and the classic Codemasters format titles
Project CARS 2 5606 Project CARS 2, Automobilista 2
Modern EA F1 20777 F1 22 through F1 25
EA Sports WRC 20777 EA Sports WRC
OutGauge 4444 BeamNG.drive

The helper listens on all of those ports at once, quietly. It detects the game from the packets themselves. Every port can be changed. It also accepts a small relay protocol (port 20780). That is for the sims that publish telemetry into Windows shared memory instead of broadcasting it: iRacing, RaceRoom, Assetto Corsa, Competizione, EVO, rFactor 2 and Le Mans Ultimate. (Shared memory is a block of memory the game shares with other programs on the same machine.) Those need logi-tf-relay running inside the game's Proton prefix to feed it. (Proton is Steam's layer for running Windows games. A prefix is the private Windows-style folder Proton keeps for each game.) The relay is attached to each release as a download. logi-launch stages it into the prefix for you. See Simulated TrueForce Internals and docs/SHARED_MEMORY_RELAY.md.

Two of those, Competizione and EVO, have TrueForce of their own. It reaches a direct-drive wheel (the RS50 or G PRO, where the motor turns the rim directly) through the shim, the small library the project places in front of Logitech's. On an RS50 or G PRO the helper never synthesises haptics for them, whatever the strength says. That would double the real thing. It runs beside the game for the rev lights and the screen only, fed by the relay. That is what puts rev lights and a dashboard into ACC on those wheels. A G923 cannot receive the game's own TrueForce. There, the simulated kind is the whole recipe.

Euro Truck Simulator 2 and American Truck Simulator are a third case. They publish through a plugin interface. So a native Linux plugin (liblogi_tf_scs.so, also a release download) forwards their telemetry. No Wine is involved. (Wine is the software that runs Windows programs on Linux.)

Playing something else that sends UDP telemetry? (UDP is the simple network packet format these games use.) See Add a Game for how to capture it and help get it added.

Enabling it, per game

  1. Open the Setup page in logi-wheel-gui or logi-wheel (see Configuring the Wheel).
  2. Find the Simulated TrueForce panel. It has a master switch, helper start/stop, and a per-game list with individual enables and intensities.
  3. Switch on the game's own telemetry setting. Examples:
    • DiRT Rally 2.0: in hardware_settings_config.xml, set <udp enabled="true" extradata="3" ...>. extradata="3" is required; the default 0 is too short to synthesise from. The stock port 20777 is the default here too.
    • Automobilista 2 / Project CARS 2: System settings, set UDP frequency to a nonzero value, protocol "Project CARS 2".
  4. Race. The helper stays silent until the game's data arrives. It stops when the data goes quiet.

The knobs

Configuration lives in ~/.config/logi-wheel/tf-sim.conf. (If you set $XDG_CONFIG_HOME, it is $XDG_CONFIG_HOME/logi-wheel/ instead.) The file is plain key=value. The Setup page edits it for you.

Key Meaning Default
enabled master switch on
follow_game_gain scale the haptics by the running game's own force-feedback strength, so its slider governs these too; a game at zero is silent on
intensity master intensity, 0 to 100 30
pitch felt rev rate, 10 to 200 percent. 100 puts the fundamental at the crank rate (rpm/60 Hz); lower feels like a slower, heavier engine 35
cylinders cylinder count, used to derive the firing rate the note is built from 4
effects mix in the haptic layers beyond the engine note (kerbs, surface, rev limiter and the rest); off is engine-only on
leds drive the rev-light display from telemetry RPM on
wheel which attached wheel to drive: auto, dd (RS50 or G PRO) or g923. rs50, gpro and 923 are accepted too auto
port.codemasters (also serves F1 and EA Sports WRC), port.pcars, port.beamng, port.relay the ports it listens on 20777 / 5606 / 4444 / 20780
game.<id>.enabled, game.<id>.intensity per-game override, applied on top of the master on / 100
screen RS50 and G PRO: show the car on the base's screen while a session runs, from the same telemetry as the rev lights off
screen.template what the screen shows: a wheel_oled frame with {gear}, {speed}, {speed_mph}, {rpm}, {rpm_pct}, {throttle_pct} and {brake_pct} filled in from the game. Both apps' screen editor writes this for you `G
g923.ffb_invert G923 only: sign of the mirrored force-feedback value in the stream (hardware-calibrated; leave alone unless forces and haptics visibly disagree) 1

The game's own slider counts too. A game's force-feedback strength reaches the wheel as a standard gain. The helper scales itself by that gain. So turning force feedback down in a game turns the engine note down with it. Zero means silence. That matters most in titles with no TrueForce of their own. There, the game's own TrueForce setting does nothing here. Its force-feedback slider is the one that reaches this. follow_game_gain=0 restores the older behaviour, where only the settings below applied.

Intensity is master x per-game. So you can set a global comfort level and trim individual games. Pitch is the one to play with if the engine feel reads too frantic or too lazy. It scales the fundamental frequency without touching amplitude.

Wheel only matters with more than one wheel plugged in. With a single wheel, auto picks it. With a G923 and a direct-drive wheel together, auto picks the G923. Set this to dd or g923 to say which one you want driven. Both apps offer it on the Setup page. So you should not need to edit the file by hand.

For a one-off run without changing your configuration, set LOGI_TF_SIM_WHEEL. It takes the same values and wins over the file.

The screen as a dashboard. On an RS50 or G PRO, screen=1 puts the car on the base's small display for as long as a session runs. It shows gear and speed by default, or whatever screen.template says. The screen goes back to the wheel's own menu when the session ends. The easiest way to set it is the screen editor in either app: LIGHTSYNC page, "Choose what to show...", then "Use during games". The editor writes both keys. It works in the lights-only mode too. An intensity of zero gives rev lights and a dashboard with no haptics at all. The G923 has no screen.

Trying it without a game

The Setup page offers a consent-gated test sweep. So does logi-tf-sim --sweep from a terminal. The sweep is a synthetic RPM run-up. You can feel the effect and calibrate intensity with no game running. Hold the rim first; it is a direct-drive wheel.

Is something already streaming to that wheel? That could be the helper itself with a game running, or a second sweep. Then the sweep refuses, and names what has the wheel. It does not take turns on an endpoint that only one program can own. It asks for the wheel before the countdown. So a refusal arrives before you have been told to hold the rim.

Good to know

  • Simulated TrueForce and games with built-in TrueForce do not fight. The helper only plays while the game's data is flowing. Games with native TrueForce support stream their own effects directly, without using the simulation.
  • One streamer per wheel. The wheel's TrueForce endpoint carries one packet per millisecond in total. Two programs writing it take turns rather than sharing. The motor then ends up buzzing at a fixed 500 Hz instead of playing either one (see Troubleshooting). So whoever streams takes a lease on that wheel first. The lease is a lock file under the runtime directory, with the holder's name in it. The kernel releases it if the holder dies, so nothing has to be cleaned up after a crash. It is per wheel, so a second wheel is unaffected. It is advisory: a program that knows nothing about it still streams. A system with nowhere to put the file carries on as before.
  • Both readers of the relay port get the telemetry. A unicast datagram goes to exactly one socket, whatever options the listeners set. So logi-tf-sim and logi-rpm-bridge cannot both read port 20780 directly. They do not have to. Whichever has the port forwards every datagram to the fan-out ports behind it (20782 to 20784). Whichever arrives second reads one of those. It also takes 20780 back if the first one exits. So the survivor keeps receiving telemetry sent where every producer sends it. You do not have to stop either program. Nothing needs a different port. LOGI_RPM_PORT and port.relay still move the whole block if a producer of yours needs a different one.
  • Time, not buffer size, bounds how far behind the engine it can get. The stream holds at most 128 ms of samples. It drops the oldest beyond that (counted, and reported). So a moment of system load costs you a fraction of a second of engine note. It does not put the note a second behind the car for the rest of the session. This was measured on the wire after fifteen seconds of continuous streaming. A change in engine speed starts coming out of the wheel 15 ms later. It has fully taken over the note by 90 ms.
  • The rev-light feeder runs at G HUB's own cadence (~60 Hz). (G HUB is Logitech's Windows software.) It writes only when the level actually changes, so a rev sweep keeps up with the engine; see Simulated TrueForce Internals. It drives the strip of the wheel it is streaming to. It stands aside entirely while logi-rpm-bridge feeds that strip during a native-TrueForce session. So the two never write different mappings over each other.
  • The helper plays through libtrueforce, the project's own version of Logitech's TrueForce support.

For how it works inside (parsers, synthesis, the watchdog loop), see Simulated TrueForce Internals.

Clone this wiki locally