Open Nipal42 opened 2 years ago
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 @Ekzilit, #6323 is relevant to your system. Can you check how it behaves with Proton Experimental?
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
Compatibility Report
System Information
I confirm:
Symptoms
When launching the game, it display a black screen and stop.
It seems that it come from DirectX12, because when I change the renderer to DirectX11 in the config file of the game, it run perfectly.
Reproduction
Launch the game with DirectX12 renderer