You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The wheel already works in G923 mode (including force feedback, but no idea on TrueForce). Altering the ID from 272 to 268 in the existing Xbox-model-related code already makes it mostly work.
I'll try to get USB dumps and post them here. I'm not that sure how to go about it in the correct way. I'm only familiar with capturing a whole bus via Wireshark. I'm specially unsure if I should do something before trying to sniff traffic from a USB passhthrough to a Windows VM with G Hub.
Output in dmesg before using hid-logitech-hidpp from here:
[226345.045696] usb 5-2.1: new full-speed USB device number 120 using xhci_hcd
[226345.153461] usb 5-2.1: New USB device found, idVendor=046d, idProduct=c268, bcdDevice=33.06
[226345.153467] usb 5-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[226345.153470] usb 5-2.1: Product: PRO Racing Wheel for PlayStation/PC
[226345.153471] usb 5-2.1: Manufacturer: Logitech
[226345.295491] input: Logitech PRO Racing Wheel for PlayStation/PC as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/usb5/5-2/5-2.1/5-2.1:1.0/0003:046D:C268.00AF/input/input268
[226345.295597] hid-generic 0003:046D:C268.00AF: input,hidraw9: USB HID v1.11 Joystick [Logitech PRO Racing Wheel for PlayStation/PC] on usb-0000:0e:00.3-2.1/input0
[226345.301507] hid-generic 0003:046D:C268.00B0: hiddev101,hidraw10: USB HID v1.11 Device [Logitech PRO Racing Wheel for PlayStation/PC] on usb-0000:0e:00.3-2.1/input1
[226345.308096] hid-generic 0003:046D:C268.00B1: hiddev102,hidraw11: USB HID v1.11 Device [Logitech PRO Racing Wheel for PlayStation/PC] on usb-0000:0e:00.3-2.1/input2
And the output when using this driver after building with a changed ID for the current Xbox code:
[33811.113930] usb 5-2.1: USB disconnect, device number 24
[33833.606816] usb 5-2.1: new full-speed USB device number 25 using xhci_hcd
[33833.721493] usb 5-2.1: New USB device found, idVendor=046d, idProduct=c268, bcdDevice=33.06
[33833.721497] usb 5-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[33833.721499] usb 5-2.1: Product: PRO Racing Wheel for PlayStation/PC
[33833.721501] usb 5-2.1: Manufacturer: Logitech
[33833.873482] logitech-hidpp-device 0003:046D:C268.0026: Setup multiaxis on the wheel
...
[33833.873527] logitech-hidpp-device 0003:046D:C268.0026: Setup multiaxis on the wheel
[33833.873529] logitech-hidpp-device 0003:046D:C268.0026: Set usage->code 0
<and many repeats>
...
[33833.873661] input: Logitech PRO Racing Wheel for PlayStation/PC as /devices/pci0000:00/0000:00:08.1/0000:0e:00.3/usb5/5-2/5-2.1/5-2.1:1.0/0003:046D:C268.0026/input/input71
[33833.930268] logitech-hidpp-device 0003:046D:C268.0026: input,hidraw9: USB HID v1.11 Joystick [Logitech PRO Racing Wheel for PlayStation/PC] on usb-0000:0e:00.3-2.1/input0
[33833.936570] logitech-hidpp-device 0003:046D:C268.0027: hiddev101,hidraw10: USB HID v1.11 Device [Logitech PRO Racing Wheel for PlayStation/PC] on usb-0000:0e:00.3-2.1/input1
[33834.005564] logitech-hidpp-device 0003:046D:C268.0027: HID++ 4.2 device connected.
[33834.073618] logitech-hidpp-device 0003:046D:C268.0026: Force feedback support loaded (firmware release 6).
[33834.077760] logitech-hidpp-device 0003:046D:C268.0028: hiddev102,hidraw11: USB HID v1.11 Device [Logitech PRO Racing Wheel for PlayStation/PC] on usb-0000:0e:00.3-2.1/input2
And then mostly works. ACC reports the wheel as another Joystick I have plugged in, but the values do come from the wheel, including those of the pedals. Force Feedback seems completely incorrect in ACC, AMS2 and R3E and probably everything else. Buttons light up in Oversteer but I'm not sure everything is correct. When the wheel clutch is configured as handbrake, acceleration axis is cut and I think becomes negative. Oversteer just shows that as an orange line. In some games the pedal axis seem inverted.
I don't know how to diagnose FFB besides starting up a race, which is quite time consuming. The test in Oversteer produces wheel effects but I don't know how correct they are.
I tried this environment variable without any result: SDL_JOYSTICK_WHEEL_DEVICES="0x046D/0xC268". It seems to me from a cursory look in SDL2 that the ID's for the PS model are already there.
Event: time 1724677244.222398, type 3 (EV_ABS), code 0 (ABS_X), value 32689
Event: time 1724677244.222398, -------------- SYN_REPORT ------------
right clutch acting as handbrake (as configured in the wheel) - values go to 65536.
Event: time 1724677296.092975, type 3 (EV_ABS), code 2 (ABS_Z), value 0
Event: time 1724677296.092975, -------------- SYN_REPORT ------------
Here is ffbwrap.log the output of ffbwrap --throttling --logger=/tmp/ffbwrap.log /dev/input/by-id/usb-Logitech_PRO_Racing_Wheel_for_PlayStation_PC_...-event-joystick. It's a few seconds of starting a test race and driving a few meters to the right out of the garage. Then the wheel starts turning unexpectedly and sometimes persists for a few seconds after opening up the menu.
The gpro-ffb-axis-6.5 branch seems to give less incorrect FFB but still it seems broken.
I get a bunch of this in the kernel log, which probably explains why FFB continues after the menu is open for a bit.
This is about https://www.logitechg.com/en-us/products/driving/pro-racing-wheel.html PlayStation/PC model.
The wheel already works in G923 mode (including force feedback, but no idea on TrueForce). Altering the ID from
272
to268
in the existing Xbox-model-related code already makes it mostly work.I'll try to get USB dumps and post them here. I'm not that sure how to go about it in the correct way. I'm only familiar with capturing a whole bus via Wireshark. I'm specially unsure if I should do something before trying to sniff traffic from a USB passhthrough to a Windows VM with G Hub.
Output in
dmesg
before usinghid-logitech-hidpp
from here:And the output when using this driver after building with a changed ID for the current Xbox code:
And then mostly works. ACC reports the wheel as another Joystick I have plugged in, but the values do come from the wheel, including those of the pedals. Force Feedback seems completely incorrect in ACC, AMS2 and R3E and probably everything else. Buttons light up in Oversteer but I'm not sure everything is correct. When the wheel clutch is configured as handbrake, acceleration axis is cut and I think becomes negative. Oversteer just shows that as an orange line. In some games the pedal axis seem inverted.
I don't know how to diagnose FFB besides starting up a race, which is quite time consuming. The test in Oversteer produces wheel effects but I don't know how correct they are.
I tried this environment variable without any result:
SDL_JOYSTICK_WHEEL_DEVICES="0x046D/0xC268"
. It seems to me from a cursory look in SDL2 that the ID's for the PS model are already there.Also
evtest
seems to work as expected.with wheel movement
right clutch acting as handbrake (as configured in the wheel) - values go to
65536
.Here is ffbwrap.log the output of
ffbwrap --throttling --logger=/tmp/ffbwrap.log /dev/input/by-id/usb-Logitech_PRO_Racing_Wheel_for_PlayStation_PC_...-event-joystick
. It's a few seconds of starting a test race and driving a few meters to the right out of the garage. Then the wheel starts turning unexpectedly and sometimes persists for a few seconds after opening up the menu.The
gpro-ffb-axis-6.5
branch seems to give less incorrect FFB but still it seems broken.I get a bunch of this in the kernel log, which probably explains why FFB continues after the menu is open for a bit.
The text was updated successfully, but these errors were encountered: