• OS: Manjaro Linux
• KERNEL: 5.16.18-249-tkg-cfs
• CPU: AMD Ryzen 5 PRO 4650G with Radeon Graphics
• GPU: AMD Radeon RX 580 (POLARIS10, DRM 3.44.0, 5.16.18-249-tkg-cfs, LLVM 13.0.1)
• GPU DRIVER: 4.6 Mesa 21.3.7
• RAM: 32 GB

I have this same issue. In addition to setting DirectX11, this can also be fixed by setting the renderer to Vulkan in $GAME_DIRECTORY/game.xml.

OpenGL is also a valid renderer option but the game crashes while loading on my system when set.

Logitech G29 wheel experienced several issues starting from 7.* version of proton (GE builds have the same issue), including:

Steering axis only detecting right turns
Accelerator pedal only working to half way down, any further and it no longer recognizes input from it.
Brake pedal not being recognized at all.

Wheel work fine only on 6.3-8 official proton.
So game is unplayable with wheel on new versions of proton (GE builds as well)

Hello @kisak-valve
6.3-8 - no issue
experimental - issue exists
next 7.0-6 - issue exists
7.0-5 - issue exists
GE-Proton7-48 - issue exists

As I remember this issue exists from the release of fs22, can be checked here https://www.protondb.com/app/1248130. Issue with wheel appears in messages from 1 year ago.

I can confirm the same results as @Ekzilit

One thing I would like to add is I found FS22 does not run when using Wayland. Works fine when using XOrg.

9 beta - issue with wheel device still exists

just like @Ekzilit I have problems with my wheel on proton > 6.3. I have not tried the pedals but my experience with the steering axis is like this.
When I turn right I works like it should, but as soon I turn it any degree to the left it steers 100% to the right.
It looks like an unsigned integer was used instead of a signed integer.

I can confirm I have the same issue as @Ekzilit with my Logitech Driving Force GT wheel. The issue seems to be related to axis in general, and not just wheels because a very similar issue plagues my Logitech Extreme3DPro joystick with the axis.

Switching to Proton 6.3-8 seems to fix the issue both for my wheel and joystick.

I have build proton 7.0-1 and here is the same issue. So the issue began between 6.3-8 and 7.0-1. The release nodes mentions "Improve Steam Input controller support for games running via Origin." I do not known if this could have a negativ effect for some non Origin games. The other part is the update to wine 7.0.

I have no problem with the wheel in snowrunner on experimental.

I've got an Titanwolf Hotas (7Axis, 2 Hats, 32 Btn) and a Thrustmaster T150 Wheel. They are configured correctly and do work as expected in native games (ATS/ETS for the T150, X series for the Hotas). In Proton games they are at least recognized, but all axis are stuck on positive values (the "left side" of the axis is stuck to max-positive).
Hats are actually working correctly.

evtest returns values from 0 to 255 for RX and RY and 0 to 1023 for all other axis
jstest returns values from -32767 to 32767 on all axis, the same goes for sdl-jstest

Tested in FS17, FS20, Mechwarrior 5, Mechwarrior Online and Bus Simulator 18 with forced hidraw and forced SDL

Configuring them as xinput-devices will resolve the stuck axis-problem, but makes those controllers unusable in native running steam-games (i.e. the t150 will not be recognized anymore in ETS/ATS) or will only allow for a limited set of buttons (Hotas).
Switching back to a Proton-version before 7.0 won't work anymore, as every game tried refuses to start.

I'm also having issues with Farming Simulator 22, any latest proton versions, Logitech G923 wheel turning axis is out of whack, turning right is as it should be but turning left it activates the same axis as the right and it's not possible to remap ot properly, also brake and accelerator only work when pressed a short distance. I'm using Heroic Launcher for epic games on Ubuntu 24 Noble Numbat, tried games on steam and they all work as they should with different proton versions, so I believe this is a proton issue.

we need to somehow get the G Hub driver to load under proton, but, at least I, can't get G Hub to install, I suspect it uses 32bit library in 64bit mode or something. that leaves the option to try to "install" the driver manually, but I'm not entirely sure how drivers even work in Windows. Like if it's just a file somewhere and some registry keys, then it might be possible, if not then we just might have to wait until Proton devs (they probably won't because we're not their target group) or vendors give us official support (they probably won't because the minority, that is Linux gamers, ain't worth their time and money)

we need to somehow get the G Hub driver to load under proton, but, at least I, can't get G Hub to install, I suspect it uses 32bit library in 64bit mode or something. that leaves the option to try to "install" the driver manually, but I'm not entirely sure how drivers even work in Windows. Like if it's just a file somewhere and some registry keys, then it might be possible, if not then we just might have to wait until Proton devs (they probably won't because we're not their target group) or vendors give us official support (they probably won't because the minority, that is Linux gamers, ain't worth their time and money)

That's how the Linux driver kernel came about with the new lg4ff driver, cause there is apparently no way of getting the windows driver out of ghub, I have the ghub installed on a windows dual boot disk but it does all the work. So they have been making the driver from scratch, there was a thread somewhere with a Logitech dev saying they were reminding their managers that the option should be thought about, to bring ghub to linux.

Replying to https://github.com/ValveSoftware/Proton/issues/5351#issuecomment-2466406457

I meant into the prefix. The problem is that it's not properly recognized by the game under Proton. Like it works flawlessly in native games, but games under Proton just don't know what to do with the data from lg4ff. Wish I knew how Windows worked with drivers. I mean if you install the legacy Logitech app into the Snowrunner prefix it kinda works. Like it's not properly properly recognized but the axis and buttons at least work..... for a few sessions. I was wondering if we could maybe tweak with the prefix's registry file or something to make it work

I have came across some files for the Logitech GHub and a couple of other that contain .dll files for the wheel, it doesn't look like a driver but there some force feedback, trues force and a logi steering wheel.dll file, I can't decompile them on my ubuntu and haven't tried to do anything with them on windows, I don't even know if they could be used for information.

I did however look on proton db to find it isn't just Logitech wheels and Joysticks that have this problem as another user is having issues with a Fanatec direct-drive wheel.

@VDubbaJ Yes you are right it is not just logitech which have the problem. I just realized that I never informed you which wheel I am using. It is a thrustmaster T248 and It is having the same problem.

I have looked a little into the history of this bug and from what I have gathered is was introduced in proton version 7. One of the things that was changed was the upgrade of the Wine version embedded in proton. Are there anyone who can test if it is a wine or proton bug.

If I look at the history of this page: https://github.com/GloriousEggroll/proton-ge-custom/blob/master/docs/CONTROLLERS.md, It was changed around the same time as version 7 was introduced and if you compare the 2 drawings it look like wine made large changes in the way it handles controller communication.

My skills with low level code and drivers very low but I hope someone with more skills that me can use my observations.

@silverlore It looks as if the Proton Versions are made to be compaitble or essentially coded to work specifically with controllers such as PS4/Xbox Gamepads instea of wheels which in Linux use HID, which means the Devs for Proton would need all the HID Sources for each device to code them in, If I'm reading the gloriouseggroll link correctly that is.

Another thing to mention, I have read on Forums people say it's cause Farming Sim is a Windows only Game and Linux will never be supported, except it plays well without using a wheel, out of curiosity I looked on Proton DB at Farming Sim 25 Latest game which says it's Platinum Playable on Linux, well the same problem is on there, people saying their different wheels are not working, inputs mapped incorrectly, turning wheels to the left and the game shoots off to the right etc, wheel only works with proton 6 but the game wont load or crashes with that proton version.

Only problem I see with that version is unlike this Thread for FS22 where we have numerous replies to say it's not working correctly, on the FS25 page there are no support or bug report threads to say it's not working correctly, essentially as far as Valve and Proton Devs are concerned the problem doesn't exist in Farming Simulator 25 because no one is reporting it, there is over 7 people at least the reports I saw on Proton DB that say otherwise.

But yeah my coding knowledge is limited also so not much I can look into.

This is because of a change in proton over wine upstream where the values are reported as signed values (with negatives also) instead. Some games play nicely with this, and some very much don't.

This also affects city car driving 2, and probably other unreal engine 5 based games (which I assume farming simulator 22/25 is).

The games that detect it as a hard right do so because negative signed values are internally the highest values of unsigned values. e.g. -127 would be 255 on an 8-bit field (however, this is a 16/32 bit field in wine/proton codebase).

The games that don't detect any leftward movement are likely just rejecting values that are way off range.

These two refactor commits from wine 7.0 appear to have caused this issue. Many steering wheels are 16 bit, and almost all are unsigned (the "simplification" makes it signed).

• https://github.com/ValveSoftware/wine/commit/d7c4867257e0388096839c3208fb6e8a7d19625e
• https://github.com/ValveSoftware/wine/commit/4a15cc9eb9665a44c8948f51d2035f2aa3ac2791

This also affects city car driving 2, and probably other unreal engine 5 based games (which I assume farming simulator 22/25 is).

@aveao Just a small correction, Farming Simulators are all based on the developers' in-house engine called Giants Engine.