Have you tried testing with both X-input and Direct-input modes? If both work, it might be worth trying both and sending logs for both. You have to restart the game after each mode change.

It would help if you could launch the game, go to the controls in-game and try to remap some buttons, including the trigger that doesn't work. Then quit the game and send the log.

FYI: Player.log is the log from the latest session (game start), Player-prev.log is from the previous session.

Nice! Thanks for confirming!

Yeah, that's how direct input works unfortunately - no analog triggers.

I suggest switching back to xinput, restarting the game and trying this: Although, if there's nothing suspicious caught in the log, there might not be much we could do.

As a side note, I found posts online about the same issue, but the only "solved" one was on the Steam forums and ended with "it's working now". If you have Steam it might be worth adding art of rally as a non-Steam app and enabling some of the additional support in Steam Controller settings so the F710 could be seen as an Xbox controller for example. I don't recall if you need to add aor as start.sh or artofrally.x64 from the game folder, though. You might also need to add -force-vulkan as a launch option.

Thank you for sharing the log! I let the team take a look just in case, but yeah, it doesn't seem to have recorded any input issues. It just looks like some incompatibility between the input system we're using and the Linux driver (especially since it works in Windows/Wine and there are other similar reports). I'm not aware of any current plans for updating that system, but maybe in the future...