-
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
No FFB in BeamNG with T300RS GT #66
Comments
This sounds like what the wheel does with no driver installed. Could you post output of |
The wheel is listed:
|
I would expect there to be at least one more message, something like this:
Note the last line, it's printed after initialization is completed successfully. Did you omit it by mistake? |
I filtered only by USB. I'll get back to you on this tomorrow. Thanks so far! |
Alright, here's all the messages about FFB or T300 I could find. Everything looks sorta OK? Besides the module verification failing. It even recognized it as an Alcantara Edition which surprised me.
After disconnecting and re-connecting. Are the "USB disconnect, device number x" messages correct even though I only disconnected and reconnected once?
|
Yep, looks like the driver is being loaded correctly.
Yep, they're fine. The wheel restarts itself after being initialized by Anycase, looks like BeamNG FFB doesn't work for me with newer Proton versions. Proton 6.3-8 seems to work, did you already try different Proton versions? |
I do get some force feedback now, but again it's only pretty much a strong self-centering force like what happens in BeamNG native which I mentioned in the first comment. |
Alright I reinstalled Fedora and set everything up again. It seems to be better, but still oscillates really badly, even parked. Tried messing around with the settings in Oversteer to no avail. When drifting the wheel also oscillates a-lot mid slide and it feels like the FFB updates only once or twice a second which causes it to be kind of choppy all the time and randomly catch up to where the wheel's actually supposed to be. |
Sounds like it's working about as well as it can work. BeamNG FFB is kind of iffy, there's a number of other reports about the game with some pretty different behavior and some hacks to work around issues. I'm guessing you already found #34? |
I've read it yeah. Sorry for the late response since I've been away from home for a while now but I decided to go back to Windows for now. |
Understandable, I'll close this issue then. |
Been at this trying to install everything for about 6 hours now. Running on little sleep so I might've done something wrong. I finally got the goddamn windows drivers to install. Running BeamNG native app has some basic force feedback but it's just self-centering and there's nothing else (no road bumps, details, etc). Running with ProtonGE the game detects my wheel, although the default assigned binds do nothing. After trying out the native version, it seems ProtonGE version has also lost access to the files or something, because there's no response curve anymore and all the settings were defaulted to 0. Can someone help me diagnose and fix? Losing hope.
The text was updated successfully, but these errors were encountered: