-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
T300 RS no constant forces in games #101
Comments
Hi, thanks for the report. I believe this is the first time anyone's mentioned Speed Dreams or Race07, so I don't really know how well they should behave with this driver. Automobilista should still work from my experience, so something funky is going on. Looks like you've installed the module correctly, as
That's normal, though rather confusing. |
I will check the Steam controller input menu soon In the mean time, I wanted to point out a few things: As I said the first time I installed the driver (a couple of months ago I believe) I went for the manual approach. I tested the wheel through Oversteer, running the linearity tests and such; Then some time passed up to some days ago when I wanted to go for a spin. At this point I though that maybe I could try a fresh install of the driver, but didn't know how to uninstall (i tried make uninstall inside the project directory) so I thought that maybe doing a reinstall would overwrite every module file. But the wheel "felt" exactly the same. That's when I tried various things like those I mentioned in the previous comment. I think it's of note mentioning the following: Speed dreams had a huge deadzone in the center, so I followed your tip on setting up a udev rule in
This didn't seem to produce any effect until yesterday when I went for another try and the deadzone was gone. Now, Oversteer has always required sudo so far to access the wheel properties (and so did fftest) but apparently this is not meant to happen. The Oversteer's readme says this:
Since About blacklisting hid-thrustmasterIn your ReadMe you wrote
but the driver is called hid-thrustmaster, with the dash, not the underscore (found in |
Yep, that is effectively what happens. Generally you would also want to restart your system to make sure the changes take effect. There are ways to avoid rebooting as well, but generally rebooting is just the easiest/safest way.
Same thing, generally a reboot is in order. I guess that could be made more clear in the README.
Oversteer generally installs the correct udev files automatically so you don't have to run it as root after that, there should be a popup that asks if you want to install the files the first time you launch Oversteer. At least when installed from GitHub the last time I installed it. Could be that something weird is going on with your permissions, though I don't think that that really explains much, as programs generally wouldn't use some effects but not others, they'd use no effects at all, as you correctly deduced.
For whatever reason the kernel module subsystem uses
Yep, and not detecting anything is in this case is what I want to see, Steam doesn't think the wheel is an Xbox controller or something. Could you still try running your games with Steam Input disabled? You can disable Steam Input on a per-game basis, |
I tried disabling steam input per game but nothing changed. However, in Automobilista control setting I noticed that by disabling "auto steering rotation" I cannot change the rotation and it's stuck at 240. In fact, forcefeedback aside the steering angle felt weird compared to last time I played the game on Windows, as if there was a mismatch between the T300 rotation and the ingame rotation, Here's a screen |
Seems plausible, I suppose? The method Linux uses to change the steering angle is by writing the angle to a special file, and I don't think Proton is aware of how to handle that. So the wheel receives inputs from Linux, that is working with some angle, and the wheel reinterprets that to be some other angle, maybe. I'm not sure if the steering wheel angle setting is something standardized into DirectInput or if it might be something provided by Anyway, thanks for checking. Do you have a way to update the firmware of the wheel? The driver should complain if it detects a firmware version too old to work for certain, but it could be that something's messed up the check for whatever reason. I'm currently away from home and I can't check how Automobilista is behaving on my computer for at least a week, sorry. |
Don't worry! Take your time :) Yesterday I checked the firmware and even reinstalled it by mistake but it was already at version 34, which seems to be the latest. In the past hour
I was thinking about installing another distro (maybe Debian or Fedora) to see if the issue persists, but that would be quite time consuming. |
Maybe try using a virtual machine, I fairly regularly spin up throwaway VMs for testing different things. I would recommend I didn't even realize Speed Dreams was open source, actually really cool. I'll have to look into how it implements its FFB, could maybe shed some light onto other games as well. |
I will try VMs once I have some time to spare, thanks for the tips :) About Speed Dreams, yeah, very cool to see! Seems to be a very old project but still in development, I read they're changing up the heads of the projects and planning, among various things, to finally move from Subversion to Git, for their version control (news post here). Then I would like to ask you some questions, @Kimplul , but they're slightly out of topic in regards to this issue, so I thought it's best to leave them out of this space. It's about getting started with linux driver development. Where can I reach you? |
Email at kimi.h.kuparinen@gmail.com if you want a private but asynchronous conversation, maybe a GitHub discussion if you don't mind it being public. For more direct contact, I do still have a Discord account, |
Actually I don't mind it being public, because it can be of use for others. Since I was not familiar enough with GitHub discussions i did a quick search that showed me that there should be a discussion section in the repo. I guess it isn't enabled here because there was no reason up to now. Or it's not available for everyone.
I don't mind this too, seems like an interesting alternative. |
Oh, sorry, haven't used them myself, I just saw the button for them and thought they might be interesting to try out, didn't realize they had to explicitly be enabled. Should be online now. |
They are indeed! I'll write a post as soon as I can. |
I looked at speed dreams, turns out that the game requested an effect with a duration of 1 second, started playing it with a replay count of effectively infinite and then just kept updating it. I thought I handled these situations properly, but the short effect duration triggered a bug that caused the driver to ignore the play count and stop the effect after one second. Speed dreams now has at least some FFB on my machine with commit cafd0f4. |
I tested the wheel some days ago but forgot to let you know that the forcefeedback finally came alive with Speed Dreams! You had to see my smile ahah! Still I managed to do a quick test on Race07 and AMS and unfortunately the issues with my system are still there; Moreover, not sure if I made a mistake, but running the constant force effect (no. 1) in fftest did not work as expected this time, since the wheel wouldn't move. I need to try again before confirming, maybe it was just a temporary hiccup. |
Hi,
I've been trying to get my T300 RS (GT edition) to work on Linux Mint 21.3.
I have installed the driver twice so far, first time manually, second time through the DKMS script.
I have tried the wheel in the following games
I tried several things, among which I
hid-thrustmaster
inblacklist.conf
Then I used fftest and everything seems to work fine since running effects 0 (periodic) and 1 (constant) does indeed make the wheel do what you would expect it to do; But it seems like the games I tried won't use such effects, and I am lead to believe that no other game will behave differently.
I browsed through closed issues and other people seemed to have solved their issue after your fixes, but I guess it's not my lucky day lol.
One thing I noticed is that when I run dmesg I still see hid-thrustmaster popping up (even though it should be blacklisted):
And running
lsmod
with the wheel plugged in looks like thisWhat should I try next?
Thank you for your efforts.
The text was updated successfully, but these errors were encountered: