Running "Test" causes game to see wheel correctly

[elite4jonny]

Wheel is Thrustmaster T300. I have installed the Linux driver and have good performance from the wheel in most games. Oversteer shows the controls all working correctly.

Game that highlights unusual behaviour is Euro Truck 2 (Free demo on steam)

In Linux native, the game has an unusually large deadzone (seems to be a common issue online) requires me to run

Evdev-joystick --e /dev --d 0 --f 0
In order to correct deadzone problem. Others online say they use proton instead for better performance (DirectX mode).

Running game in Proton 9 DirectX mode it's like the wheel (Thrustmaster T300) is always fully turned to the right hand side. Game settings show the wheel is turned fully right during calibration, even if the wheel is turned left and right. Opening Oversteer before the game doesn't correct the behaviour. Opening Oversteer and running the wheel test, then opening the game causes the buttons on the wheel to be remapped, but it can be used correctly and the wheel input registers as expected. Closing oversteer or rebooting the computer causes the game to again fully steer to the right, and opening Oversteer and running the test again corrected the behaviour.

What is the test doing to remap the controls, shouldn't this be happening as soon as the software is started?

[berarma]

This is totally unexpected. Oversteer doesn't remap the controls at all. It could be an error in Proton or the driver, or both. The test only removes any existing effects, sets the rotation range, gain and autocenter, and creates some effects. When finished it deletes effects and restores range, gain and autocenter values.

[elite4jonny]

I agree, absolutely unexpected behaviour but appears to be reproducible. Is there any troubleshooting I could do, a before/after log of the inputs I could find somewhere, because somehow oversteer is fixing whatever bug this is!

…

On Thu, 11 Jul 2024, 18:49 Bernat, ***@***.***> wrote: This is totally unexpected. Oversteer doesn't remap the controls at all. It could be an error in Proton or the driver, or both. The test only removes any existing effects, sets the rotation range, gain and autocenter, and creates some effects. When finished it deletes effects and restores range, gain and autocenter values. — Reply to this email directly, view it on GitHub <#214 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE6HKVT6FQP5OZSDIELP5BTZL3AQ3AVCNFSM6AAAAABKTUQZ6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRTGUZTENJRGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[berarma]

You could try changing range, gain and autocenter values from Oversteer and see if those changes have any effect.

[berarma]

@Kimplul

[Kimplul]

Thanks for the ping, took me a few days to find a bit of time to look into this but I can replicate, specifically the DX11 version of the game seems to behave this way. Adding open_mode=0 to modprobe seems to fix this, could be that it's related to a comment @berarma made a few years ago by now: Kimplul/hid-tmff2#56 (comment)

I'll play around a bit more and check if it's tied to some specific Proton version, not entirely sure what the best fix would be but one option could be to set open_mode=0 by default in the driver. This would have the slight downside that the wheel's autocalibration throws it off center when plugged in, but I guess that's not too bad.