Feedback and encountered problems #21
Comments
|
I think F1 2020 has issues on every wheel, it behaves strangely. It might be related to some bug in Wine/Proton. EDIT: this might have been the case for F1 2019 instead. |
|
Hi, thanks for the report. F1 is unfortunately a known issue, my current leading theory is that it for some reason checks from some database which wheels it's aware of, and the T300RS (at least the configuration under Linux) isn't on it. As such, the wheel is considered by the game to be a gamepad and disables most effects. There was some discussion about it in #17, and I sent a patch to SDL but I don't think it's been released yet. Sort of unprofessional, but I haven't tested if my patch actually works, since I'm working over the summer in another part of the country and don't have the wheel with me. I suppose it could also be that F1 detects some kind of conflict between its database and the wheel's reported featureset. I haven't added the FF_CUSTOM effect, and if the game tries to use it and fails it might go into a 'failsafe' mode of sorts where only Or, as @berarma pointed out, a bug in Wine. Anyway, in short, F1 is on my todo-list, but it might take me a while to actually get around to it due to not currently being able to test anything. Sorry about that. |
|
Thanks for the explanation. I appreciate it!
Should I close this issue or leave it open for now?
…On Wed, Jul 7, 2021 at 10:10 AM Kimplul ***@***.***> wrote:
Hi, thanks for the report.
F1 is unfortunately a known issue, my current leading theory is that it
for some reason checks from some database which wheels it's aware of, and
the T300RS (at least the configuration under Linux) isn't on it. As such,
the wheel is considered by the game to be a gamepad and disables most
effects. There was some discussion about it in #17
<#17>, and I sent a patch to
SDL but I don't think it's been released yet. Sort of unprofessional, but I
haven't tested if my patch *actually* works, since I'm working over the
summer in another part of the country and don't have the wheel with me.
I suppose it could also be that F1 detects some kind of conflict between
its database and the wheel's reported featureset. I haven't added the
FF_CUSTOM effect, and if the game tries to use it and fails it might go
into a 'failsafe' mode of sorts where only FF_RUMBLE is supported. I
tried contacting Feral Interactive about the issue but haven't gotten a
response.
Or, as @berarma <https://github.com/berarma> pointed out, a bug in Wine.
Anyway, in short, F1 is on my todo-list, but it might take me a while to
actually get around to it due to not currently being able to test anything.
Sorry about that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGCYYTDGJFMAD4XCEMNAP3TWQDWVANCNFSM476DCPIQ>
.
|
|
Leave it open for now, as the issue hasn't been resolved and the other discussions about the topic have mentioned it more as a sidenote. |
|
Please, take a look at this. berarma/oversteer#67 It might be that the game is sending ffb updates too fast. It seems to be a problem for the G920. The user tried to use a workaround in ffbtools but it didn't work for him. |
|
Thanks!
I gave that a go but ffbwrap does not seem to have any effect. Not sure if it’s logitec specific? Tried it with options like inverse on a few games and it didn’t do anything at all.
Oh just adding to my previous post. BeanNG does work just fine, I just had to invert the FFB for some reason. The game has an option for that luckily.
… On 07 Jul 2021, at 14:22, Bernat ***@***.***> wrote:
Please, take a look at this. berarma/oversteer#67
It might be that the game is sending ffb updates too fast. It seems to be a problem for the G920. The user tried to use a workaround in ffbtools but it didn't work for him.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
I compiled and install that patched version of SDL you mentioned here. Is there anything I should do after installing it? Does steam not used a packaged version of SDL? Or would it use the system one if it exists? |
|
Success with that patch btw. I built it in 64bit mode and used LD_PRELOAD when running the game. I now have FFB 🗡️ e.g. of my steam launch command LD_PRELOAD=$LD_PRELOAD:~/git/SDL/build/.libs/libSDL2-2.0.so.0.14.1 %command% |
|
Eyyyy, that's cool. Thanks for testing it out, really appreciate it, and thanks @berarma for pointing out the SDL function. I recommend still leaving this open for now, I'd like to get an understanding of which games use SDL to detect wheels and features. We also noticed that DiRT rally treats the wheel as a gamepad in the settings, but still uses full FFB, and I think Euro Truck Simulator had some similar issues, and they might all be linked to SDL. |
|
Glad I could help! Just another note, I had to disable steam controller support on the game properties otherwise the throttle would just be stuck at 100% all the time. After turning that off and remapping the pedals everything just worked. Completed two races now and no funnies :) |
|
Right, I got to mess with the wheel this weekend.
Sometimes Euro Truck Simulator 2 twitches a bit, apparently it generates a single sine pulse that it likes to sometimes play. For some reason, it also sometimes reverses the direction of the pulse, switches again and repeats a couple times. Occasionally, this is accompanied by a pretty big spike in the effect strength, which results in some twitching. Not really sure what I should do about it, since the spike is "visible" in |
Can you post the ffb log lines where the pulses happen? I did a bit of debugging using ETS2 for the G29 wheel. Are you using the demo? I think there were differences between the demo and the game some time ago. |
|
Here's one, they're usually pretty similar. If you'd prefer the whole logfile, I can add it to the repo somewhere. The 'spike' I was talking about is the magnitude rising to about 2000, in this case 1914 at max, with direction changes between almost every packet. The magnitude at 'idle' is about 200-400, and highest peak I've so far seen was about 2700. This was captured with the full game. |
|
I remember fixing some corner cases with periodic effects, like maintaining the phase when updating an effect that is playing. I think it's not the case here since the effect is stopped before updating. I guess those effects simulate the irregular rumble of a truck engine. I don't have the time to look at the code but I hope you don't mind that I try to help by throwing some guesses. ETS2 seems to send ffb updates as fast as it can. Limiting fps by setting vsync on could change the way ffb works. Also, in the driver, you could check that:
You can use |
|
I don't mind at all, thank you. Could you elaborate on what you mean by:
I noticed that the wheel handles negative periodic magnitude to an extent, but manually phase-shifting the wave 180° resulted in slightly less twitching. And by magnitude I'm referring to the magnitude that's sent to the wheel, so effect magnitude scaled by effect direction. Since the effect direction changes 180° in this case, it essentially just switches the magnitude's sign. Anyway, this technically doesn't respect the phase as requested by the effect upload, but instead more closely resembles what the effect "intends".
I'll probably need to double-check this, although in ETS2's case the play count is just one, followed by a stop command. I wonder if I maybe handle frequent start/stop pairs in a dumb way, as at the moment a stop command doesn't clear the `FF_QUEUE_PLAY-bit, so in theory if the commands are close enough to eachother I could be sending a start and immediately after a stop, due to how my current queue-system is implemented. Don't know if it is at all related, but something that came to mind.
No such warnings in |
|
Just noting here. F1 2021 also works great just like 2020. Still using the same launch command as earlier. @Kimplul Do you know if that SDL patch has made it mainline yet? |
|
It's present in the 2.0.16 release. Don't know which version your distro ships with, but seems like the patch is getting out there. EDIT: Run |
|
Hello guys, |
|
Doing some winter cleaning, the SDL patches are presumably widely distributed by now so I think it's fine to close this. |
Hi,
Off the bat, I would like to that you for your efforts on this. It's great to finally have my wheel working nearly perfectly on Linux :)
I could not find a thread indicating which games have been tested so I made a shortlist of tested games and encountered problems.
Let me know if I can be of some assistance to help debug/test fixes for known issues.
The text was updated successfully, but these errors were encountered: