Skip to content
coasting-ncPublic

About

A Telemetry-based Force Feedback app for LMU and RaceRoom.

Topics

Resources

Stars

166 stars

Watchers

3 watching

Forks

Latest commit

 

History

76 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Coffee Donate to Support this App

FFB-HUB (previously called LMUFFB)

A Telemetry-based Force Feedback app for LMU and RaceRoom.

LMUFFB is being renamed FFB-HUB as we expand support for additional racing simulators.

Coffee Support FFB-HUB: Make a donation

If you find this app useful, consider contributing to support ongoing development, making the app easier to setup, better default profiles, bug fixes, and compatibility with more simulators (RaceRoom, Assetto Corsa EVO, and others).

Some of the advantages of this app (with the right settings and a direct drive wheelbase) are:

  • Usually clearer FFB than with in-game FFB. Driving cues are easier to feel.
  • You can still get some FFB improvements even in lower-end wheels (G29, T300), or DDs at 3-5 Nm
  • Brake Feel and Understeer effects in RaceRoom
  • Brake Feel effect in LMU
  • For LMU, being able to catch power oversteer slides out of corners thanks to the Yaw Kick effects
  • For LMU, more noticeable detail at comfortable (lower) force levels, while with the game FFB you usually have to make the FFB very strong in order to feel details that remain very subtle.
  • FFB-HUB avoids having too strong FFB where it is not needed, and too weak when it is needed. The app gives a nicer, more balanced, more informative FFB experience.
  • Some drivers describe the improvement in FFB that you can achieve with this app as much greater than the differences between direct drive wheelbases.
  • Being able to customize the FFB to tailor it to your preferences. Reduce effects you find excessive and emphasize the information you find useful.

For example, in RaceRoom’s GT3 cars at Bathurst, in turn T3/T4 you can feel the load shifts as you go up and down on the track undulations, and you can tell if it is the front or the rear of the car that is washing out.

lmuFFB GUI

📥 Download

Installation & Configuration

For both LMU and RaceRoom:

  1. Extract the zip to a folder where you can write files, such as a folder in Downloads. Do not use Program Files.
  2. Start FFBHUB.exe
  3. Select your wheel under FFB Device.
  4. Choose LMU or RaceRoom using the Game selector at the top of the app.
  5. Run the game in Borderless Mode or VR (you can run the game before or after the app, it does not make any difference).
  6. In RaceRoom, turn off FFB.
  7. For LMU, turn off “Use Constant Steering Force Effect” (to prevent the game from trying to take control of the wheel and send FFB), and set FFB Strength to 100% (the maximum) which allows the app to properly scale the wheel strength when using In-Game FFB option as the "Torque Source" in FFB-HUB.

When not in VR, make sure the game Display Mode is Borderless (Prevents crashes/minimizing).

Help us improve the app

  1. Report issues - For bugs and technical issues, it is much better to open a GitHub issue rather than posting on forums.
  2. For LMU, post screenshots, thoughts and settings to the LMU Forum Thread for the lmuFFB App

Troubleshooting (LMU)

  • I am getting excessive oscillations while on straights:
    • Try setting "Smart Hands-off Protection" to 10% - 20% or more (it should work on GT3s, but might not for LMP2s and Hypercars).
    • Increase at least to 1.0 the "Threshold" slider for "Yaw Kick" and "Power Yaw Kick" (if they are enabled).
  • I am getting too much vibrations while braking:
    • Reduce "Lockup Strength" of the "Lockup Vibration" effect (e.g., down to 20%).
    • Increase Steering Shaft Smoothing ("Front Grip" section) to 8 ms.
    • Also adjust the other settings of the "Lockup Vibration" effect (you might need different settings per car class):
      • Gamma: increase this to make the effect start weaker and more progressively.
      • Start slip: increase this to delay the start of the effect, requiring more tire slip to trigger.
      • End slip: increase this to make the effect reach its maximum strength later.
      • Sensitivity: increase this to make the effect trigger later, requiring more wheel angular deceleration.
  • Unable to save settings or config.ini errors:
    • This usually happens if you placed the FFB-HUB app or folder in a location without write permissions (e.g., inside C:\Program Files).
    • Solution: Keep the entire FFB-HUB app folder to a location where the app can have full write access, such as a subfolder in your Downloads folder.
  • Inverted FFB (Force pushes away from center):
    • If the FFB feels "backwards" or "inverted" while driving (wheel pushes away from center instead of pulling toward it), check the "Invert FFB" checkbox in the FFB-HUB app GUI.
    • This reverses the force direction to match your wheel's expected behavior.
  • No FFB:
    • Ensure the "FFB Device" in FFB-HUB app is your real wheel
    • Check if Connected to Le Mans Ultimate" appear in the GUI
    • Verify the FFB strength in your device driver is not too low
    • Increase Master Gain or reduce Max Torque Ref
    • Check the FFB-HUB app console for errors
  • FFB too weak:
    • Increase Master Gain (slider ranges from 0% to 200%, so you can boost beyond 100%).
    • Or reduce Max Torque Ref (this amplifies the signal by setting a lower reference point for maximum torque).
  • Violent oscillations or shaking:
    • If you experience violent oscillations that the Smoothing or Speed Gate settings don't catch, try increasing Max Torque Ref (e.g., from 45 to 60-80 Nm).
    • Higher Max Torque Ref values reduce clipping and noise, which can cause oscillations.
    • Tuning Tip: Max Torque Ref is the primary way to control the balance between clipping/noise and steering weight. Start at 45 Nm and adjust based on your preference.
  • Strange pull in some scenarios:
    • If you feel a strange pull in specific driving situations, try reducing the Rear Align Torque.
  • Sharing Presets:
    • You can now easily share your FFB settings with others using the "Export Selected..." and "Import Preset..." buttons in the Presets section.
    • Exported presets are saved as small .ini files that can be sent to other users.
  • The app has too many options and it's confusing:
    • A future version will include a "Basic Mode" with auto adjustment and defaults for most settings.
    • We need to first determine which settings work best for most users and wheel types (Direct Drive vs Belt/Gear).
    • Please leave feedback on the forum thread telling us what settings work best for you: LMU Forum Thread
  • Any other issue:
    • Preferred: Open a GitHub Issue. This is the best way to ensure your issue is tracked and addressed. Our AI agents periodically scan and attempt to fix GitHub issues.
    • Alternatively, post in the LMU Forum Thread, but be aware that forum posts are harder to track.

Clarification about the Interaction Between In-Game FFB (from LMU) and the FFB from the App

The app takes exclusive control of the FFB sent to your wheelbase, which means that it is the only program sending force feedback to your wheelbase. This is required by DirectInput, and it is the reason why the app displays "Game FFB is blocked."

However, among the many telemetry channels that it uses, the FFB-HUB app includes a specific telemetry channel called "In-Game FFB", which allows you to still include the LMU original FFB signal within the final FFB that the app produces.

How it Works

The "In-Game FFB" stream is the FFB produced by LMU. It is mostly based on the Steering Rack Torque (which is why in the app you can select it as one of the two possible steering torque sources), plus any additional effect and processing that LMU might be doing on it behind the scenes (eg. adding damping, smoothing, vibrotactile effects, etc.).

This stream is impacted by any setting that you might change from the game FFB Settings (see below).

You can control the impact of the In-Game FFB on the final FFB produced by the FFB-HUB app in several ways:

  • You can enable or disabled it: by selecting "In-Game FFB" as your Steer Torque Source in the app, it will be combined with all other telemetry-based forces processed by the FFB-HUB app to produce the final FFB you feel.
  • Game Settings: Any changes you make to LMU's internal FFB settings (strength, smoothing, vibrotactile effects, etc.) should directly affect what the FFB-HUB app receives through this channel.
  • In App Gain slider: The "In-Game FFB Gain" slider in the FFB-HUB app acts as an additional multiplier to change the strength of this specific channel.

In-Game FFB (400Hz) vs. Shaft Torque (100Hz Legacy)

In the App ("Front Grip" section), you have two options for your base steering torque ("Steer Torque Source"):

  1. In-Game FFB:

    • Pros: High sample rate (400Hz), includes LMU's built-in processing (eg. smoothing) and specialized effects (eg. vibrotactile effects).
    • Cons: if you don't like the game built-in processing.
  2. Shaft Torque (100Hz Legacy):

    • Pros: A "pure" source of steering rack torque information without game-side processing.
    • Cons: Lower sample rate (100Hz), potentially slightly higher latency (though usually unnoticeable), and may require gain adjustments via the "Steering Shaft Gain" slider, because it might have a very different baseline strength compared to In-Game FFB.

FAQ

Q: Does the app constitute an unfair advantage ("cheating")?

A: No. Multiple wheelbase manufacturers already provide or are implementing telemetry-based force feedback (including VNM, Simucube, and Simagic). By the same logic, those would constitute an "unfair advantage" too.

Additionally, bassshakers/transducers, active pedals, motion platforms, and other simracing equipment also give similar additional telemetry-based information (tire lockup, wheelspin, car behavior, etc.), and are not considered an unfair advantage either.

The app allows everybody to have the option of having additional telemetry-based feedback information, not just the owners of expensive equipment or particular wheelbases.

Q: Does the app have an option to remove the feeling of flatspots vibrations from FFB? Is that an unfair advantage?

A: No. The app had a "Notch Filter" option that is also present in Simucube wheelbase software (and possibly other wheelbases), so that is a legitimate feature. The feature was supposed to reduce specific user-defined frequencies from the FFB signal, like in the Simucube software. It was improperly named "Flatspot Suppression", but it could attenuate any frequency, like in other wheelbase software. Early testing suggested it was not actually doing anything (it wasn't working). The feature has in any case been removed in recent versions of the app, since it was a legacy effect that was not working and was not really necessary for the app.

Q: How is the app getting the telemetry data from the game?

A: The app is using the official LMU Shared Memory Interface that was introduced with LMU 1.2 in December 2025.

Upcoming Features

  • Basic mode with only main sliders and auto adjustments of more advanced settings
  • Wet Weather Haptics (Hydro-Grain): vibration cues telling when the tires are on dry or wet surface, and if there is grip or not. This tries to replicate some the particular wet track grip and dynamics that can be felt in real life cars.
  • Support for other Sims (AC Evo, RaceRoom, AC, ACC, rF2).

Feedback & Support

For feedback, questions, or support:

  • GitHub Issues (Recommended for Bugs): Report bugs or request features. GitHub issues are easier for us to track and are periodically tackled by AI development agents.
  • LMU Forum Thread: lmuFFB App. Best for general discussion and sharing settings.

Licensing & Project Status

As of April 11th 2026, this project has transitioned to a proprietary, closed-source model.

Statement on Independent Development and Licensing:

  • Ownership & Originality: The current codebase is entirely proprietary and owned solely by the author. It has been developed independently from scratch.
  • No Third-Party GPL Code: This software does not use, fork, incorporate, or depend on code from any other GPL-licensed projects.
  • Transition from Open-Source: Prior to April 11th 2026, an early prototype of this project was briefly hosted as open-source under the GPL license.
  • Purging of Community Contributions: To ensure complete compliance with open-source licenses, all of the previous minor contributions by external developers (including merged pull requests and community-suggested code snippets) have been entirely discarded and rewritten from scratch using clean-room, independent implementations. No community-contributed code remains in the current codebase.

We take intellectual property rights seriously and have taken exhaustive measures to ensure this software is entirely independent.

Documentation

Note: this documentation is not up to date.

Videos, Reviews and Tutorials

UKOG: This FFB App is Blowing Up… But is it Actually Better? (Le Mans Ultimate)

UKOG

Gamer Muscle: This FFB App Completely Transforms LMU – Full Setup, Profiles & Download

Gamer Muscle

For the RaceRoom side of the app: Gamer Muscle: RaceRoom FFB Just Got A HUGE Upgrade! You NEED This App! - FFB-HUB

Gamer MuscleRR

Dalking: LMU FFB App Explained in Detail | Settings, Effects & My Setup

Dalking

Dalking's video is an excellent step by step guide for setting up the app from scratch for LMU, tuning each effect in the most effective order, and explaining what each effect does.

To find and share lmuFFB profiles, see:

About

A Telemetry-based Force Feedback app for LMU and RaceRoom.

Topics

Resources

Stars

166 stars

Watchers

3 watching

Forks

Releases

Packages

Used by

Contributors