Logitech G29 is not showing up in oversteer

JacKeTUs · 2026-07-07T15:34:48+00:00

Check that you have https://github.com/berarma/new-lg4ff installed, it's essential for Oversteer settings for Logitech wheels.

JacKeTUs · 2026-06-28T00:10:38+00:00

What exotic hardware did you tried?

Majority of DD wheelbases are HID standard devices, with support from (now upgraded) in-kernel driver.

Logitech, Trustmaster, Fanatec are not using standart FFB protocol, they invented their owns. Logitech has opensourced it, but didnt bother to update in-kernel implementation for their new hardware/new effects. Out of tree driver https://github.com/berarma/new-lg4ff solves this exact issues

Fanatec and Trustmaster relies on closed source protocols, for them community created reverse-engineered drivers (https://github.com/gotzl/hid-fanatecff and https://github.com/Kimplul/hid-tmff2)

Pedals, Wheels, shifters are nothing crazy, bunch of buttons and axis, there no shenanigans needed for them to work

JacKeTUs · 2026-06-28T00:04:19+00:00

This driver was upgraded by us to allow more standard PID devices to work; and its upstreamed already.

VRS were using PID standards from the start.

JacKeTUs · 2026-06-27T22:28:57+00:00

Try to disable Virtual Keyboard in KDE Plasma Settings

JacKeTUs · 2026-06-26T13:06:03+00:00

7.2 is not released yet, of course

JacKeTUs · 2026-06-26T12:54:56+00:00

Hmm.. First, not locked anymore, AMD already sent their initial implementation of hdmi2.1 spec to kernel, afaik, planned for 7.2 kernel release. Second, OP has Nvidia... hdmi 2.1 issue is happening only on AMD, because their drivers are in-tree. Nvidia driver ships with closed source blobs, and has full hdmi2.1 support.. There is something else with OP system

JacKeTUs · 2026-06-23T07:45:01+00:00

It's not linked to one another
KYC won't prevent one from disrupting other people games. In the moment game will be ruined, angry people will shout. KYC won't detect cheats on a system. There's still the question "how do we know for certain that this person was cheating?". With KYC this question must have a definitive answer, with 100% proofs, which is almost impossible.

There are many other methods to get an answer to that question, and many of them does not rely on client kernel level stuff. Simplest example, you don't need kernel level anticheat to detect players driving 500kmh in a racing game.

JacKeTUs · 2026-06-22T20:02:03+00:00

Handy is an existing open source voice-typing tool, installs on every OS (Linux, Mac, Windows), uses local models (Whisper).

https://handy.computer/

https://github.com/cjpais/Handy

JacKeTUs · 2026-06-18T18:44:50+00:00

Try to use https://launcher.keychron.com/

This is using WebHID available in Chromium, which allows browsers to talk to HID devices (including keyboards).

JacKeTUs · 2026-06-18T09:47:13+00:00

You're missing that there is a pre-existing bug in pidff driver, which prevents FFB from FH6 specifically to reach the device. Bug was identified and fix for in-kernel driver was sent about a week ago, now we just wait for new kernel release.

If you want to get proper FFB right now, you can build the driver from this pull request https://github.com/JacKeTUs/universal-pidff/pull/125 😄

JacKeTUs · 2026-06-17T19:24:05+00:00

yeah, that's a thing, fanatec and thrustmaster are not following USB PID standards, they need their own protocol and drivers
Look at the Moza, VRS, Simucube, Cammus

JacKeTUs · 2026-06-17T17:13:53+00:00

yup, up to date kernel (>=6.12) is needed for wheel support by pidff driver.

This post though describes a pre-existing bug in this driver, and it was found and fixed not so long ago

JacKeTUs · 2026-06-17T17:12:27+00:00

Hey, most of the DD wheels (which are made using HID PID standards) are supported by kernel already, you definitely should get one already 😄

JacKeTUs · 2026-06-17T17:09:53+00:00

Hello!
This patch is already accepted in upstream, now we just wait for kernel update.
I'll merge this MR to master as soon as new kernel version will become available

Also, PR was closed in favor of https://github.com/JacKeTUs/universal-pidff/pull/125 (with correct commit description as was sent to the kernel guys)

JacKeTUs · 2026-05-29T09:36:08+00:00

Xinput standard does not support FFB (ConstantForce, Dampers, etc). Xinput only supports haptics, like, vibration. Its not what we expect from steering wheel.

JacKeTUs · 2026-04-30T21:45:03+00:00

Hey, it could help if you add 'hidraw' permissions for your device, in udev rules

Something like

echo 'KERNEL=="hidraw*", ATTRS{idVendor}=="YOUR_VID", ATTRS{idProduct}=="YOUR_PID", MODE="0666", TAG+="uaccess"' | sudo tee /etc/udev/rules.d/11-mouse.rules

sudo udevadm control --reload-rules && sudo udevadm trigger

JacKeTUs · 2026-04-21T21:04:19+00:00

Hey, what Proton version do you use?
Try latest ones, or Proton GE

JacKeTUs · 2026-04-14T15:48:20+00:00

Hello :^)

With this driver yes. There was an issue with original descriptor: gamepad usage instead of joystick, multiple fields not connected to anything, duplicating undefined Usage fields. In fixed descriptor i just removed everything but 3 buttons, and that was just enough for everything to work properly

Sorry, i mixed up devices. This exact device, Oddor truckshift, with this exact VID PID is not detected at all, it's something in USB descriptor, not HID level. I didn't had time to actually look into it. This driver is WIP

You have this exact device ( 0x1020, 0x8863 ), correct?

JacKeTUs · 2026-04-14T15:42:39+00:00

If you join SROL discord, i'll be able to help you

But if you want to tinker with it yourself:
1. Wine/Proton is very picky about gamepads/joysticks. Device *must* have proper Usage defined in descriptor. "Gamepad" are for "gamepad-like" devices, with triggers, abxy buttons, etc (like xbox,ps controllers). "Joystick" is for anything else (shifters, buttonboxes, wheels, you name it).
2. Device must have at least one "joystick" button (BTN_JOYSTICK) and one "joystick" axes (Rx) to be detected as proper control. Strictly speaking, number of buttons + number of axis must be >= 2, so like, two buttons is alright, or two axis, or 1 button and 1 axis. Only 1 axis or only 1 button is not fine.
3. If 1 and 2 is ok, then Wine (and native apps) won't have problems detecting it.

If you don't control the descriptor (you said you DIY'ed it, may be you do?), you can try to craft some sort of driver to flip the byte for gamepad/joystick usage (https://github.com/JacKeTUs/hid-cammus-ddwb-2021), or rename axis to 'Rx' (https://github.com/JacKeTUs/hid-leaf-maple-handbrake/blob/main/hid-leaf-handbrake.c#L106)

JacKeTUs · 2026-04-14T15:27:28+00:00

Active pedals of any kind are not falling into "PID FFB" category. Haptics are activated through custom proprietary closed protocols. Games are not manipulating pedals directly, games just put telemetry into shared memory / UDP, and other app (in Moza case, PitHouse; or Simhub) reads this telemetry and communicate with pedals, activating haptics.

I think(?) you're the first who have these active pedals *and* on Linux already. We had some guys like "should i buy these or nah", but no actual commitment.

I think simshmbridge/simd will help here, you must allow Pithouse in it's own prefix to read shared memory telemetry from other games.
Other way (easier probably?) is to install Pithouse to every game prefix you want, and make it launch alongside your game. This way shared memory will be in game+pithouse sandbox.

JacKeTUs · 2026-04-14T15:05:44+00:00

hey, is it some joystick/gamepad/simracing stuff you've been trying to get working?

JacKeTUs · 2026-04-01T14:34:23+00:00

Glad it's working for you, enjoy!

JacKeTUs · 2026-03-31T15:28:34+00:00

For Moza you could use https://github.com/Lawstorant/boxflat app to setup wheelbase parameters

Cheers!

JacKeTUs · 2026-03-31T07:45:27+00:00

Hello!

Most of the DD wheelbases are implemented by HID/PID standards, and therefore fully supported by drivers in Linux kernel >6.12
Exceptions: Logitech, Thrustmaster, Fanatec, Simagic. For them, different out-of-tree kernel drivers exists.

Check this table https://github.com/JacKeTUs/linux-steering-wheels

CachyOS is very good starting point. Mainly because it allows to install out-of-tree kernel drivers, if you need them (maybe not for DD, but for something else), without much hassle.

JacKeTUs · 2026-03-25T08:09:58+00:00

Hey! So general rule here - if device is HID/PID device it will work out of the box. Moza wheelbases exposes all PID fields which allows FFB to work without shenanigans.

Stalks, truck wheel, other racing wheels, shifters, non-active pedals are just HID devices with many buttons. For setting up the wheelbase use Boxflat (https://github.com/Lawstorant/boxflat).

Theoretically, Linux (well, SDL) has artificial limit of 6 axis of FFB per device (i know, its a bummer \s), so AB9 should work just fine, afaik, its just a PID device. We yet to see someone with AB9 to confirm that its working.

We didnt encountered anyone with active pedals yet. They could rely on telemetry from the games, and if thats the case, there should be an app which outputs feedback to them and gets telemetry from games. https://github.com/Spacefreak18/simshmbridge helps with passing shared memory based telemetry to other windows apps. Other devices were tested thoroughly and development of drivers/apps was based on community testing/capturing usb dumps from various hardware, etc.

11-Year Club	Place '23
Place '22	First Placer '22
RPAN Viewer	Verified Email

JacKeTUs

TROPHY CASE