Fanatec BMW GT2 wheel - missing analog binding/axis. #109
Comments
|
This sounds similar to #77 |
|
Hello I used the most recent version of the driver. I tried evtest on the wheel and indeed, it seems like the axis values are all wrong: That was me moving the stick all the way to the left and right, then up and down. However, running the command mentioned in the issue you linked does not in fact callibrate the axes correctly for me, despite axis 3 and 4 being listed as ABS_RX and ABS_RY for me. The wheel is confirmed as working under Windows. Could it be an issue with my firmware? |
|
Can you check/post the calibration with |
|
The analog stick isnt mappable for a couple of games on Windows too. It's a problem on fanatecs side. |
If I wiggle the stick, more values show up, but they only show up at the very extremes of the range of the stick: Running the It seems like it does not detect the entire range of the movement of the stick, as moving the steering wheel little by little produces a lot of messages, while wiggling the stick into extremes causes very few event readings.
It is mappable in the games that I'm trying in Windows. I know ACC has an input for "look left/right" and only accepts buttons, but in ETS2 and ATS there is a mappable look axis. Side question - is there any reason as to why I have to reset my deadzone for the device every time I start it up? |
|
Hi, the problem here seems to be the Note that you've to execute the command for each axis. Line 16 in 4f80db5
You shouldn't have to. There is the udev rule that should take care of that. Check the output of |
there is a
It did fix that issue indeed, I'm getting a lot of values now read by the stick and I can bind them in ATS and ETS2 now. I went ahead and reinstalled the driver again, copying the github repo and all. Restarted my PC and udev rules seem to be working now - both the wheel deadzone and the stick are fine. |
|
A recent update to my system broke this again, and also reset the udev rules for the rest of the wheel. I'm starting to believe something makes the udev rules break during a full update. Weirdly enough, the ones I have set up for my Thrustmaster pedals seem to be untouched, but I had to reinstall the driver yet again - not only the stick axis was borked, so was the deadzone for main steering axis. |
What do you mean by that? Was the .rules file removed by your system update? What system is it? |
|
The udev rules were still there, but they were not being applied, despite udevadm test stating that the rule was being called. I noticed that my deadzone was off again when that happened. I'm running Fedora 41. |
|
Is there another rule afterwards that does s.t. to the device? Or is there some service running that tries to apply some 'calibration' for the device? |
|
What I can see from udevadm test is that these two files get called: I don't have any services that could in theory mess with the wheel. What I've noticed is that each time this happens, when launching ETS2 it pops up with a message saying that my wheel is missing, and then I have to select a "different" wheel with the same name as my original. My axis bindings return but they have lots of fuzz and deadzone. It's as if the system was forgetting about that device altogether. If that is of any help, I do connect my wheel through a powered USB hub. |
|
Another message because I think I'm starting to figure out why this happens. The Fanatec module gets installed every time into a new kernel directory: For whatever reason though, this no longer works as well. Right now I just run by hand to fix the issue. |
|
Yes, looks like the reason for all this are the kernel updates. Unfortunately, out-of-tree modules like this one have to be compiled/installed again specifically for every kernel. Also, after you've recompile/installed the module, you've to reconnect (or power-cycle) the wheel for the module to get loaded (or load it by hand with In the udevadm log you've posted one can see that the rule is there, but it actually doesn't do anything. Most likely because the hid-fanatec module wasn't loaded for the device. udevadm output should contain a line like this: and at the bottom |
Hello,
I've recently tried the Fanatec driver under Linux using a native version of Euro Truck Simulator 2. I could bind all buttons and axis from the rest of my controls - all pedals (V3), the shifter and the wheel controls are bindable and work well, except for the left analog stick present on the GT2 wheel. Is there a workaround for this?
The Proton version of ETS2 doesn't detect that input either.
The text was updated successfully, but these errors were encountered: