Looking for G923 owners on Linux
The G923 (all variants: 046d:c266 PS, 046d:c26d/046d:c26e Xbox) speaks the same TrueForce stream protocol as the RS50 and G PRO - confirmed on Windows by the Trueforce-For-All project, with owners of both variants running TrueForce haptics there.
On Linux, the G923's normal force feedback already works through the in-tree HID++ path (nothing changes there). What has never been tested is TrueForce on a G923 under Proton - and as of current master, the pieces are in place:
- the udev rule now grants hidraw access for all three G923 PIDs, which is what lets Logitech's own SDK DLLs reach the wheel from inside Proton;
- the TrueForce shim installer and the per-game setup are the same as for the RS50/G PRO.
What to try
- Install the driver per docs/GETTING_STARTED.md (steps 1-3, including staging the SDK DLLs and
PROTON_ENABLE_HIDRAW=1).
- Launch a TrueForce sim (ACC and AC EVO are the verified ones on RS50).
- Drive over kerbs / rev the engine and tell us whether you feel high-frequency haptics on top of normal force feedback.
What to report (either way)
- Wheel variant and
lsusb | grep 046d
- Whether normal FFB kept working
- Whether TrueForce haptics appeared
dmesg | grep -iE 'g923|hidpp' and, if you're up for it, a short USB capture (tools/linux_game_capture.sh)
A negative result is just as valuable - it tells us whether the SDK's device check accepts the G923 identity via hidraw, which is the one unknown we cannot test without the hardware (this project develops on an RS50).
Looking for G923 owners on Linux
The G923 (all variants:
046d:c266PS,046d:c26d/046d:c26eXbox) speaks the same TrueForce stream protocol as the RS50 and G PRO - confirmed on Windows by the Trueforce-For-All project, with owners of both variants running TrueForce haptics there.On Linux, the G923's normal force feedback already works through the in-tree HID++ path (nothing changes there). What has never been tested is TrueForce on a G923 under Proton - and as of current master, the pieces are in place:
What to try
PROTON_ENABLE_HIDRAW=1).What to report (either way)
lsusb | grep 046ddmesg | grep -iE 'g923|hidpp'and, if you're up for it, a short USB capture (tools/linux_game_capture.sh)A negative result is just as valuable - it tells us whether the SDK's device check accepts the G923 identity via hidraw, which is the one unknown we cannot test without the hardware (this project develops on an RS50).