The Wheel Base should be set to 'PC mode' for the driver to be selected (CSL Elite and CSL DD: red LED)
- 0EB7:0E03 FANATEC CSL Elite Wheel Base
- 0EB7:0005 FANATEC CSL Elite Wheel Base PS4
- 0EB7:0020 FANATEC CSL DD / DD Pro / ClubSport DD Wheel Base
- 0EB7:6204 FANATEC CSL Elite Pedals
- (experimental: 0EB7:0001 FANATEC ClubSport Wheel Base V2)
- (experimental: 0EB7:0004 FANATEC ClubSport Wheel Base V2.5)
- (experimental: 0EB7:183b FANATEC ClubSport Pedals V3)
- (experimental: 0EB7:0006 Podium Wheel Base DD1)
- (experimental: 0EB7:0007 Podium Wheel Base DD2)
- (experimental: 0EB7:0011 CSR Elite/Forza Motorsport Wheel Base)
This is a out-of-tree kernel module. Building it depends on
- compiler (gcc)
- make
- kernel-headers
Examples of installing kernel-headers for some distros:
Ubuntu: sudo apt install linux-headers-generic or sudo apt install linux-headers-$(uname -r)
Fedora: sudo dnf install kernel-devel
Arch: pacman -S linux-headers
make
sudo make installReload the new udev rules, depending on the Linux distribution, without rebooting:
sudo udevadm control --reload-rules && sudo udevadm triggerThis installs the kernel module hid-fanatec.ko in the hid dir of the running kernel and puts fanatec.rules into /etc/udev/rules.d. These rules allows access to the device for games group and sets deadzone/fuzz to 0 so that any wheel input is detected immediately.
The driver should get loaded automatically when the wheel is plugged.
If you don't want to compile and install manually, following is a list of known packaged distributions.
| System | Package |
|---|---|
| AUR | hid-fanatecff-dkms |
This driver implements a Linux force-feedback (FF) driver, allowing force-feedback effects to be uploaded via the standard Linux libinput API. These effects are translated into a custom HID protocol and sent to the device asynchronously, using a timer that defaults to 2ms.
Supported are a bunch of effects, the code is largely copy-pasted/adapted from new-lg4ff.
Currently, FF_FRICTION and FF_INERTIA effects have experimental support in this driver.
Additionally, the driver integrates with the Linux LED interface, enabling control of the RPM and other LEDs found on most Fanatec wheel rims. This is achieved by writing to the appropriate sysfs files. Further details on these and other sysfs files exposed by the driver can be found in the Device-Specific Section.
Wine/Proton provides multiple methods for accessing HID devices. Typically, it interfaces with the Linux libinput subsystem either directly or through SDL, using this information to create a corresponding Windows input device. While this allows games to utilize HID and force-feedback functionality, it does not support LEDs or other advanced features.
Notably, the Fanatec SDK—used by certain games—often encounters issues when interacting with the Windows input device created in this manner.
As an alternative, Wine/Proton can use HIDRAW to create Windows input devices directly from a device’s HID descriptor. This approach allows Wine/Proton to communicate with the device as if running in a native Windows environment, enabling proper interaction with the Fanatec SDK for LED and display control.
For force feedback to function correctly in Wine/Proton using HIDRAW, the HID descriptor must expose HID PID functionality. To achieve this, the driver extends the device's HID descriptor with the necessary HID PID components and exposes them through the HIDRAW interface. HID PID commands from Wine/Proton are intercepted, translated into the custom HID protocol, and sent to the device. All other communication is directly passed through.
By default, HIDRAW is not enabled in wine. To enable it, see the EnableHidraw registry key.
The Proton wine fork maintains a hardcoded list of devices for which HIDRAW is enabled. Beginning with Proton ?, HIDRAW is enabled for Fanatec wheel bases by default (prior versions of Proton will fall back to the Linux libinput/SDL method). To force using libinput/SDL set PROTON_ENABLE_HIDRAW=0 %command% as launch-option.
Games that are expected to work (tested by me and others more or less regularly):
| Game | compat-layer | libinput-FFB | hidraw-FFB | hidraw-FanatecSDK | Notes |
|---|---|---|---|---|---|
| AC | proton | yes | yes | no | |
| ACC | proton | yes(*) | yes | yes | |
| ACE | proton | no, crash on startup | yes | yes | |
| Automobilista 2 | proton | no, crash on startup | yes | no | includes FanatecSDK but doesn't drive LEDs/display |
| BeamNG.drive | native | yes | - | - | |
| BeamNG.drive | proton | yes | yes | no | |
| DiRT 4 | proton | yes | ? | ? | |
| DiRT Rally 2(**) | proton | no, crash on stage-load | yes | no | |
| WRC(**) | proton | no, crash on startup | yes | yes | can't be played anymore due to anti-cheat |
| F1 2020/2021 | proton | yes | yes | no | FFB is weak and some effects seem to be missing, see (#22) |
| F1 2X | proton | no, crash on startup | yes | yes | FFB is weak and some effects seem to be missing |
| rFactor2 | proton | yes | yes | yes | need to set negative FFB strength |
| Rennsport | wine/proton | no, crash on startup | yes | yes | |
| RRRE | proton | yes | yes | yes | |
| Wreckfest | protno | yes | ? | ? |
The libinput-FFB denotes if the game/FFB works when using Windows input device derived from libinput/SDL.
The hidraw-FFB column denotes if the game/FFB works when using Windows input device derived from hidraw device.
In case of the latter, the hidraw-FanatecSDK column denotes if the FanatecSDK is able to drive LEDs/display.
(* input devices can get mixed-up; best have only the wheel-base connected and always use the same USB-slot)
(** uses experimental FF_FRICTION effect)
(*** unsure if all effects are present)
Advanced functions of wheels/bases are available via sysfs. Generally, these files should be writable by users in the games group. Base sysfs path:
/sys/module/hid_fanatec/drivers/hid:fanatec/0003:0EB7:<PID>.*/
- Set/get range: echo number in degrees to
range - Get id of mounted wheel:
wheel_id - Tuning menu (experimental):
tuning_menu/*- Get/set 'standard'/'advanced' mode:
andvanced_mode - Get/set tuning menu slot: echo number into
SLOT - Values get/set:
BLI DPR DRI FEI FF FOR SEN SHO SPR ...(files depend on wheel-base) - Reset all tuning sets by echoing anything into
RESET
- Get/set 'standard'/'advanced' mode:
- RPM LEDs:
leds/0003:0EB7:0005.*::RPMx/brightness(x from 1 to 9)
- RPM LEDs (combined with base)
- Display:
display(negative value turns display off)
- Loadcell adjustment:
load(no readback yet)
- pedal vibration:
rumble- 0xFFFF00 -> both pedals should rumble
- 0xFF0000 -> throttle pedal rumble
- 0xFF00 -> break pedal rumble
- 0 -> stop rumble
To access advanced functions from user space please see the hid-fanatecff-tools project which also aims to support LED/Display access from games. Note that some games natively support LEDs/display by using the FanatecSDK and HIDRAW, see the compatible games list.
- Support more effects
- Support more devices / advances functions of devices
- Support different wheels-rims and their quirks
- Packaging for more distros
Check permissions ls -l /dev/hidrawXX, if it is not 0666, then check with udevadm test /dev/hidrawXX if there are any additional rules overwriting the mode set by the fanatec.rules file.
Check correct driver module version is loaded: modinfo hid-fanatec | grep hidraw.
Check game log PROTON_LOG=1 WINEDEBUG=+hid,+input,+dinput %command%, ensure that there is a line called found 3 TLCs. If it is not there, then a proton/wine version is used that doesn't support multi TLCs (yet).
- Clear enumerated HID devices:
protontricks -c "wine reg delete 'HKLM\System\CurrentControlSet\Enum\HID' /f" <appid> - If using separated pedals, 'pump' a pedal (to generate input) during game startup (seen in F1 23, AMS2, ??)
Check the deadzone/flatness/fuzz settings:
evdev-joystick -s /dev/input/by-id/usb-Fanatec*-event-joystick
This should output s.t. like ... flatness: 0 (=0.00%), fuzz: 0) for all axis.
If this is not the case then check that the udev rule works. Execute
udevadm test /dev/input/by-id/usb-Fanatec*-event-joystick
and see if /etc/udev/rules.d/99-fanatec.rules gets called.
Edit input/devices/device_defines.xml and add a line like this
<device id="{00200EB7-0000-0000-0000-504944564944}" name="ftec_csl_dd_pc" priority="100" type="wheel" />
Adjust the 00200EB7 to your PID (first 4 chars).
Try to delete My Documents/Assetto Corsa Competizione/Config/controls.json
Note: You'll probably have to re-map all your Buttons!
If you have an issue, feature request or a general question, feel free to open a ticket on GitHub.
I am not associated with Endor AG/Fanatec. I take absolutely no responsibility for any malfunction of this driver and their consequences. If your device breaks or your hands get ripped off I'm sorry, though. ;)
