[Bug] PROTON_ENABLE_HIDRAW needs specific device address

[kangaro0]

Category

Force Feedback

Description

Hey,

first of all thanks for your amazing work and your constant updates with new features & the gui-applications!

I need to set PROTON_ENABLE_HIDRAW to "0x046d/c27" instead of "1". Otherwise there is no force feedback ingame. Trueforce started working from v0.32.0, but I may have skipped some versions. I tried using the new method "logi-launch %command%" but there is also no ffb ingame.

Game: Assetto Corsa EVO
OS: Arch Linux 7.1.6-arch1-1
Driver Version: 0.33.0
Installation: build by source (sudo ./tools/setup.sh)

If you need additional information I'm happy to provide them.

Kind regards,
Johannes

Steps to Reproduce

1. Install driver
2. Set "PROTON_ENABLE_HIDRAW=1 %command%" in launch options
3. Start race

Kernel Version

7.1.6-arch1-1

Driver version

v0.33.0

Distribution

Arch Linux

Installation Method

DKMS

dmesg Output

[    4.731521] usb 1-4.1: Manufacturer: Logitech
[    4.737258] input: Logitech MX518 Gaming Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.0/0003:046D:C08E.0002/input/input5
[    4.737346] hid-generic 0003:046D:C08E.0002: input,hidraw1: USB HID v1.11 Mouse [Logitech MX518 Gaming Mouse] on usb-0000:00:14.0-4.1/input0
[    4.738266] input: Logitech MX518 Gaming Mouse Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.1/0003:046D:C08E.0003/input/input6
[    4.788716] hid-generic 0003:046D:C08E.0003: input,hiddev97,hidraw2: USB HID v1.11 Keyboard [Logitech MX518 Gaming Mouse] on usb-0000:00:14.0-4.1/input1
[  115.178889] usb 1-12.1: Product: RS50 Base for PC
[  115.178889] usb 1-12.1: Manufacturer: Logitech
[  115.190290] Logitech RS50 Base for PC: Invalid code 768 type 1
[  115.190291] Logitech RS50 Base for PC: Invalid code 769 type 1
[  115.190292] Logitech RS50 Base for PC: Invalid code 770 type 1
[  115.190292] Logitech RS50 Base for PC: Invalid code 771 type 1
[  115.190293] Logitech RS50 Base for PC: Invalid code 772 type 1
[  115.190293] Logitech RS50 Base for PC: Invalid code 773 type 1
[  115.190293] Logitech RS50 Base for PC: Invalid code 774 type 1
[  115.190294] Logitech RS50 Base for PC: Invalid code 775 type 1
[  115.190294] Logitech RS50 Base for PC: Invalid code 776 type 1
[  115.190294] Logitech RS50 Base for PC: Invalid code 777 type 1
[  115.190317] input: Logitech RS50 Base for PC as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12.1/1-12.1:1.0/0003:046D:C276.0009/input/input23
[  115.190624] hid-generic 0003:046D:C276.0009: input,hidraw8: USB HID v1.11 Joystick [Logitech RS50 Base for PC] on usb-0000:00:14.0-12.1/input0
[  115.191410] hid-generic 0003:046D:C276.000A: hiddev101,hidraw9: USB HID v1.11 Device [Logitech RS50 Base for PC] on usb-0000:00:14.0-12.1/input1
[  115.192203] hid-generic 0003:046D:C276.000B: hiddev102,hidraw10: USB HID v1.11 Device [Logitech RS50 Base for PC] on usb-0000:00:14.0-12.1/input2
[  115.208682] hid_logitech_dd: hid-logitech-dd v0.33.0 loaded
[  115.222477] logitech-dd 0003:046D:C276.0009: RS50 (native): Claiming interface 0 for steering-position tracking
[  115.222505] input: Logitech RS50 Base for PC as /devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12.1/1-12.1:1.0/0003:046D:C276.0009/input/input24
[  115.222549] logitech-dd 0003:046D:C276.0009: input,hidraw8: USB HID v1.11 Joystick [Logitech RS50 Base for PC] on usb-0000:00:14.0-12.1/input0
[  115.288604] logitech-dd 0003:046D:C276.000A: hiddev101,hidraw9: USB HID v1.11 Device [Logitech RS50 Base for PC] on usb-0000:00:14.0-12.1/input1
[  115.291409] logitech-dd 0003:046D:C276.000A: HID++ 4.2 device connected.
[  115.315508] logitech-dd 0003:046D:C276.000A: RS50 (native): Initializing force feedback...
[  115.317744] logitech-dd 0003:046D:C276.000B: RS50 (native): Letting hid-generic handle interface 2
[  115.317776] logitech-dd 0003:046D:C276.000B: hiddev102,hidraw10: USB HID v1.11 Device [Logitech RS50 Base for PC] on usb-0000:00:14.0-12.1/input2
[  115.472364] logitech-dd 0003:046D:C276.000A: RS50 (native): Effect timer ready (interval=1ms, 4 texture samples/tick, starts on effect play)
[  116.530449] logitech-dd 0003:046D:C276.000A: RS50 (native): serial 2528WDF083C8, base FW U1 65.02.B0037, motor FW SC 02.01.B0042
[  116.616423] logitech-dd 0003:046D:C276.000A: HID++ features (base): 8040=0A 807A=0B 807B=0C 80A4=0D 80D0=0E 8120=0F 8123=10 8127=11 8130=12 8132=13 8133=14 8134=15 8136=16 8137=17 8138=18 8139=19 8140=1A
[  116.628423] logitech-dd 0003:046D:C276.000A: RS50 (native): Current mode: desktop (profile 0)
[  116.734413] logitech-dd 0003:046D:C276.000A: RS50 (native): Force feedback initialized (full effect palette; conditions emulated host-side, textures via TrueForce)

Current sysfs Values (if relevant)

/sys/class/hidraw/hidraw*/device/rs50_*:

Game/Application

Assetto Corsa EVO

USB capture (recommended for FFB / wheel-state bugs)

No response

Checklist

• I installed the driver via setup.sh (or dkms-update.sh)
• I verified the driver loaded (lsmod | grep hid_logitech_dd)
• I checked dmesg for errors

Additional Context

logitech-trueforce-linux-driver doctor

[1/7] Kernel module
  PASS hid_logitech_dd is loaded (version: v0.33.0)
  PASS module matches this checkout (v0.33.0)
  PASS logi-wheel on PATH (logi-wheel 0.33.0)
  PASS logi-ffb on PATH (logi-ffb 0.33.0)
  PASS logi-tf-sim on PATH (logi-tf-sim 0.33.0)
  PASS logi-wheel-gui on PATH (logi-wheel-gui 0.33.0)
  PASS DKMS package installed (survives kernel updates)

[2/7] Wheel
  PASS wheel on USB: 046d:c276 Logitech, Inc. RS50 Base for PC
  PASS all 3 wheel interfaces bound to our driver

[3/7] Driver health
  PASS wheel_* sysfs present (/sys/class/hidraw/hidraw9/device)
  PASS firmware: base: U1 65.02.B0037 motor: SC 02.01.B0042
  PASS range=1080 strength=62% mode=desktop
  PASS wheel_range_restore on (puts the range back if a game moves it)

[4/7] Permissions (udev)
  PASS udev rule installed
  PASS logi-ffb uhid udev rule installed
  PASS hid-logitech-dd modprobe.d config installed
  PASS settings writable as root

[5/7] TrueForce SDK DLLs (only needed for TrueForce in Proton sims)
  PASS all four SDK DLLs staged (Trueforce 1_3_11) in /mnt/hdd/repositories/logitech-rs50-linux-driver/sdk

[6/7] Steam prefixes (shim)
  PASS TrueForce shim present in all 1 installed SDK sim(s)

[7/7] Per-game launch options
  WARN appid 3058630: PROTON_ENABLE_HIDRAW=1 not found in launch options (needed for TrueForce; set it in Steam > Properties)

Summary: 19 pass, 1 warn, 0 fail

[mescon]

To get native TrueForce and full force feedback on the RS50:

1. On a Windows machine with G HUB, copy the whole Logi folder to ~/.local/share/logitech-trueforce/sdk, so you end up with .../sdk/Logi/Trueforce/<version>/trueforce_sdk_x64.dll. These cannot be redistributed, so this is the one manual step.
2. Open Logi Wheel, Setup, find Assetto Corsa EVO, click Install TrueForce files.
3. Launch options: logi-launch %command% and nothing else. Remove your PROTON_ENABLE_HIDRAW entirely.
4. Properties, Controller, Disable Steam Input.

---

What was happening, step by step:

With PROTON_ENABLE_HIDRAW=1, the wheel goes into raw mode. In that mode the game expects Logitech's SDK to drive the wheel, and the DLLs above are that SDK. Without them nothing is driving it, so you get no force feedback at all. That matches what you saw.

With PROTON_ENABLE_HIDRAW=0x046d/c27, Proton did not recognise that as naming your wheel. It looks for the exact text 0x046D/0xC276 inside whatever you set, so your value matched nothing and it was the same as not setting it. The wheel stayed on the normal Linux input path, where force feedback works fine with nothing installed. That FFB was real and was the game's own, not a simulation. What that path cannot carry is the game's TrueForce, which only reaches the wheel through Logitech's SDK in raw mode.

So raw mode is an upgrade once the DLLs are there, and a straight downgrade before that. logi-launch was turning it on without checking whether they were, which is our bug and is fixed on master. It now declines until the files are present, and falls back to simulated TrueForce meanwhile.

[kangaro0]

Hey, thanks for the quick response!

I updated my wheel with the GHub software to avoid any incompabilities with newer trueforce dll's and copied the files from my windows vm to the folder mentioned. Furthermore I changed the launch options in AC EVO to "logi-launch %command%".
In logi-wheel-gui -> Setup it tells me that for AC EVO the TrueForce files are installed.

I didn't update the driver, that is still on v0.33.0. (git checkout v0.33.0).

But there is still no force feedback ingame.

Tree of .local/share/logitech-trueforce

.local/share/logitech-trueforce/
└── sdk
    └── Logi
        ├── Trueforce
        │   └── 1_3_12
        │       ├── trueforce_sdk_x64.dll
        │       └── trueforce_sdk_x86.dll
        └── wheel_sdk
            └── 9_1_1
                ├── logi_steering_wheel_x64.dll
                └── logi_steering_wheel_x86.dll

7 directories, 4 files

EDIT:

Setting PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=descriptor_heap PROTON_ENABLE_HIDRAW=0x046D/0xC276 gamemoderun %command% as launch options as mentioned in your commit also doesn't produce any force feedback.

[mescon]

Thanks, that rules out the files being missing. So hidraw is on and the DLLs are there, which is exactly the combination that works on my machine. That points at Proton rather than at your setup.

Two things would narrow it:

cat /tmp/logi-launch.log

and which Proton build AC EVO runs under (Properties, Compatibility). PROTON_ENABLE_HIDRAW regressed in Proton 10.0-1 (ValveSoftware/Proton#8672), while 9.0-4 and GE-Proton9-27 were unaffected. If you are on 10.x, forcing GE-Proton as a test would be telling. I am on GE-Proton and proton-cachyos here, which may be the whole difference.

One free check while you are in there: when hidraw is genuinely active on this wheel the pedals read inverted in game, resting as fully pressed. If yours behave normally, hidraw never engaged whatever the variable says.

[kangaro0]

I was using Proton 11, switched to GE-Proton-10-32 (newest version on my system). Didn't make the ffb work though.

When I first launched the game with the updated launch options and went to test it out, I noticed that the car was fully reving. As soon as I touched the wheel (probably turned it a little bit), the revs went to 0. From there the pedals behaved like normal (0 pedal -> 0 revs).

Output of cat /tmp/logi-launch.log

[logi-launch] plan: wheel=direct-drive game=Assetto Corsa EVO (early access) hidraw=1 ffb=native relay=none tfsim=0
[logi-launch] set PROTON_ENABLE_HIDRAW=1
[logi-launch] no in-prefix relay needed for this game

EDIT:

When I use GE-Proton9-27 the wheel constantly generates an "UP"-signal, like when pressing the joystick up and I can't navigate the menus.

[mescon]

0.34.0 should fix this. On the raw HID path, a game that drives force the older Windows way had nowhere to send it, so force feedback went silent. The driver now supplies what that path was missing, on by default.

Update, replug the wheel, and launch AC EVO with logi-launch %command%. You should have force feedback and the game's own TrueForce at the same time.

[kangaro0]

Hey, it's still not working. I tried multiple Proton and GE-Proton versions: Proton 11, Proton Experimental, Proton Hotfix, GE-Proton9-27, GE-Proton11-5.

I also removed the wine prefix completely as the "UP"-problem was appearing on other Proton versions after I first used GE-Proton9-27 and reran "./tools/setup.sh shim" after creating the new prefix.

Now in AC EVO settings the wheel gets shown as "RS50 Base for PC", but I can't setup a configuration. When I want to set for example the steering and the game prompts me to input the steering axis just nothing happens when I turn the wheel. The same is true for every other button or pedal.

I double checked that Steam Input is disabled.

[mescon]

Before anything else, which version are you actually running? You mentioned building from a v0.33.0 checkout earlier, and the fix is in 0.34.0, so that alone may explain the force feedback.

logi-wheel --version
modinfo -F version hid-logitech-dd
cat /sys/module/hid_logitech_dd/parameters/inject_pid

The last line matters for your new symptom. 0.34.0 changes interface 0's HID descriptor by default, and a game reading the wheel raw re-parses it. If you are on 0.34.0 with that showing 2, that is my first suspect for the dead inputs, and I want to know before recommending anything else.

[kangaro0]

Hey, thanks for staying with me.

I updated to the new version as you proposed.

[herb@archdesk ~]$ logi-wheel --version
logi-wheel 0.34.0

[herb@archdesk ~]$ modinfo -F version hid-logitech-dd
v0.34.0

[herb@archdesk ~]$ cat /sys/module/hid_logitech_dd/parameters/inject_pid
2

EDIT: Ran the last command without the wheel turned on, but updated it now.

[mescon]

Holy crap I'm so stupid. I introduced a new bug a while back that fuzzied the actual reason for the error. The issue is the DLL file isn't actually fed to the game since a couple versions back; the path to the DLL resolves incorrectly, so thats why. Holy crap. Ill be back with an update.