Workaround to get FFB to work on Linux + Proton

Hello!

I found a workaround to get FFB working on Linux with latest versions of Proton.
I only tested with my Logitech G920 and Proton 8, but if you go to the FFB settings and change the Update Type to Full it seems it solves all FFB issue I had previously.

 

Thank you! This fixed it for me as well.

In my case, FFB was completely absent while driving until I changed the setting as per the OP.

Logitech G29 (PS3 mode) with new-lg4ff DKMS module (compiled from git). I believe I was using the latest version of Proton during testing, though I will update the post when I make sure and may test the native version later.

 

I attached the log, but it doesn't seem like anything stands out.

 

Hello,

Sorry for the late reply, just realized there were answers in this thread.

Yes the symptoms were like @lightwo described, absolutely 0 FFB, it's really like the motor is completely off.
The issue appeared in later versions of Proton (version > 6.3-8).
Before FFB was working but not properly (weird behaviors, including sudden feedback in opposite direction, not accurate to simulation, ...)
With recent Proton versions and Full Update, FFB works great.

 

Hi all.
I just talked with Berarma, the creator of Oversteer (steering wheel config app) and the Linux Logitech driver new-lg4ff , and he said me that FFB updates are sent but no "PLAY" command is sent for the steering wheel to execute them.

I don't know if I should mention this here, but the native version of BeamNG hasn't worked on my computer for some time. When you are loading the stage the application crashes.

 

You should get in touch with him ( https://github.com/berarma ), I am just a mere messenger who barely understands what he is talking about.

 

Sort of a bump here, but I wanted to say Thank you. This method still works. I was scratching my head with this one. I am using Arch btw)

 

Hi @stenyak ,

I did a bit of a trace on the "Fast" update type on proton, on steam beamng (0.32.5.0 according to the launcher), there's a lack of IDirectInputEffect::Start and I don't think I see DIEP_START used with IDirectInputEffect::SetParameters

Do windows drivers play effects on SetParameters even without DIEP_START? Or is BeamNG starting the effect by some other ways in "Fast" update type?

ref:https://learn.microsoft.com/en-us/previous-versions/windows/desktop/ee417952(v=vs.85)
ref:https://gitlab.winehq.org/wine/wine...6efde38bd88e/dlls/dinput/joystick_hid.c#L2531

Thanks in advance

 

Awesome! Thank you.

 

@stenyak Thank you so much for fixing the issue, it just works now on 0.33.1.0!

For those who are interested, I've made a bug entry regarding wine's always report playing on IDirectInputEffect::GetEffectStatus' behavior on linux over at https://bugs.winehq.org/show_bug.cgi?id=57085#c0 . If I read the code correctly, wine relies on SDL for force feedback, and since SDL linux does not support querying effect status (likely due to https://bugzilla.kernel.org/show_bug.cgi?id=219189 , the lack of an interface for it in the first place), wine sets all effects as playing on linux as a result.

Once again thank you so much for the wine specific work around!