hid-tmff2
hid-tmff2 copied to clipboard
Kimplul
FFB not working (Fedora 36 dkms-install)
FFB is not working for me, and I am kind of lost how to solve this. Can someone please explain what possibly can go wrong? FFB isn't working for F1 2021 and Assetto Corsa Competizione.
Hi, could you specify if other games work or if F1 and AC are the only ones not working?
It's a fresh install and I only tries those. But I could try other games as well. What game usually works well?
If no games you've tried work, it's likely the driver isn't properly loaded or you have some weird version of the wheels that doesn't play well with the driver as it is written.
For the first option, try running dmesg -w and plugging your wheel in. If hid-tmff2 shows up without an error staus, it should be properly loaded.
I mainly play DiRT rally, works on my machine ™.
This is the output of dmesg -w
I will try DiRT Rally tomorrow. As far as I know it's a normal T300 RS GT.
Yep, driver is loaded and seems to be initialized correctly as far as I can tell. Curious to see if DiRT works.
Oh, and did you install the Windows driver inside the games' Wine prefixes? Apparently some games rely on metadata the driver installer provides, which could affect how the game behaves. I'm not sure about which games exactly, as this is still a relatively new discovery and I haven't looked into it too deeply but there's some great info courtesy of @raboebie in https://github.com/Kimplul/hid-tmff2/issues/46
Yes I installed the driver for both F1 and ACC, but it is still not working. It might be relevant to mention that I installed Steam as flatpak, maybe this could make problems with the driver?
The same issue with the wheel, but on Manjaro 21.3.7 "Ruah". The fftest tool is generating FFB. Steam is not a flatpack install.
I've set the proton version to the latest available. It's the beta version. Could try to switch to the 7.X version?
Seems like the issue was that I didn't test 0e47624ebbed48e922fe27170364aebf79217e7b properly. Turns out that I had a bug in how I was updating the duration of different effects, and that commit exposed it, but not so that I would've noticed. Sorry.
Try out the master branch, F1 at least works for me. For some reason AC and ACC refuse to start, I'll try out some different proton versions.
EDIT: Got ACC running, seems to work alright. AC still refuses to launch.
F1 is working fine for me, ACC launches as well. AC is not installed right now unfortunately.
Codecov Report
Base: 47.52% // Head: 49.16% // Increases project coverage by +1.63% :tada:
Coverage data is based on head (
f46da7b) compared to base (a52cf88). Patch coverage: 70.37% of modified lines in pull request are covered.
Additional details and impacted files
@@ Coverage Diff @@
## master #57 +/- ##
==========================================
+ Coverage 47.52% 49.16% +1.63%
==========================================
Files 41 42 +1
Lines 3825 3726 -99
==========================================
+ Hits 1818 1832 +14
+ Misses 2007 1894 -113
| Impacted Files | Coverage Δ | |
|---|---|---|
| mlchain/config.py | 50.00% <0.00%> (-3.25%) |
:arrow_down: |
| mlchain/workflows_sync/limiter.py | 76.11% <0.00%> (ø) |
|
| mlchain/__init__.py | 85.71% <71.42%> (-4.77%) |
:arrow_down: |
| mlchain/workflows_sync/pipeline.py | 73.80% <73.80%> (ø) |
|
| mlchain/server/base.py | 41.80% <100.00%> (+1.00%) |
:arrow_up: |
| mlchain/workflows/__init__.py | 100.00% <100.00%> (ø) |
|
| mlchain/workflows_sync/__init__.py | 100.00% <100.00%> (ø) |
|
| mlchain/workflows_sync/parallel.py | 70.96% <100.00%> (ø) |
|
| mlchain/base/log.py | 51.78% <0.00%> (-16.08%) |
:arrow_down: |
| mlchain/server/flask_server.py | 40.57% <0.00%> (-0.82%) |
:arrow_down: |
| ... and 7 more |
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
@detrophy
FFTEST will somewhat work, but only if I set the correct device (event23, not 0).
Could you clarify what you mean by this? Typically you would use something like
fftest /dev/input/by-id/usb-Thrustmaster_Thrustmaster_T300RS_Racing_wheel-event-joystick
The wheel itself is working, but no FFB.
I'm guessing you mean that games accept input from the wheel, i.e. you can drive around in games but there's no FFB?
Is there anything I could provide to you that will help pinpoint the issue?
Sure, first of all which games have you tested? Did you try rebooting after installing the newer version? Which wheel are you using, and in which mode (if applicable)?
@detrophy
FFTEST will somewhat work, but only if I set the correct device (event23, not 0).
Could you clarify what you mean by this? Typically you would use something like
There is some feedback, but not all. Oversteer can center the wheel, as an example.
fftest /dev/input/by-id/usb-Thrustmaster_Thrustmaster_T300RS_Racing_wheel-event-joystick
fftest /dev/input/event23
Maybe it's just the default fftest goes to, but it is defaulting to event0 instead of 23
The wheel itself is working, but no FFB.
I'm guessing you mean that games accept input from the wheel, i.e. you can drive around in games but there's no FFB?
This is correct. Everything works fine. All input. Only FFB that is not working correctly. I also tried installing the TM drivers in the steam game prefix (/home/detrophy/.local/share/Steam/steamapps/compatdata/805550/pfx/) but this didn't change change anything.
Is there anything I could provide to you that will help pinpoint the issue?
Sure, first of all which games have you tested? Did you try rebooting after installing the newer version? Which wheel are you using, and in which mode (if applicable)?
Currently only ACC, as this is the only game I game with the wheel. Yes, I did a reboot, multiple times between steps when necessary.
I'm using the T300RS GT in the PS3 mode, not inverted. The firmware version is 34
Pretty weird, ACC works for me with Proton 7.0-4, and if fftest works then the driver seems to be loaded. I also upgraded my wheel's firmware to 34 but works just fine. Do you have any other games to try the wheel with? Also, I'm assuming you have FFB turned on in ACC? There should be a small FFB gauge in the bottom right of the screen, does it show anything while you're driving?
To check if there is no mistake from my side or by a misconfiguration, I've uninstalled steam, oversteer and tmff2 and removed all modules and the dkms installation. I will try to reinstall tmff2 later on without dkms installation.
Edit: no, AC wouldn't even start and the problem solving steps mentioned on other sites weren't working, as the installation of dotnet wasn't successful.
Are you both talking about Assetto Corsa Competizione? I have the feeling you are talking past each other. @Kimplul should Assetto Corsa 1 be working again by now?
ACC, Steam Flatpak, Proton Experimental, Firmware 31, tmff2 e2dd7bdc3a22ac8b8551db4154fa36fcc631b402 is working on my machine (fedora 36).
Are you both talking about Assetto Corsa Competizione?
By ACC I'm referring to Assetto Corsa Competizione, yes.
should Assetto Corsa 1 be working again by now?
Don't know, can't get it to launch. The guides on ProtonDB haven't worked for me, so I can't test the game. In theory it should, though.
So, I've done some more testing on my side. Checking double I'm not the one with a defect configuration here.
I've found out that the game is using the wheel, even when the steam controller support is set to off and setting it to "default" will then enable FFB.
Can someone confirm this is the same with other systems and I'm not running into a bug?
I am unfortunately quite busy at the moment. I will try to confirm this on thursday.
Can't confirm, FFB works for me with both default and disabled per-game controller settings. I also tried turning on generic controller configuration but FFB still works. Strange.
@Wunderharke I see you've installed the Windows driver. When I did this (the installation failed, on windows when you click trough the setup, it closes and the installer with progressbar gets open, this didn't happen on Linux for me). After this the wheel wasn't even recognized by Dirt Rally 2 or Steam. Removing correct folder from ~/.steam/steam/steamapps/compatdata fixed this for me. Maybe the windows driver creates some random issues for you too, did you try to run things without it?
After reinstalling the games they worked with and without installing the driver somehow.
I think this issue is solved. I am available for some testing if issues return.