Bernat

The ffbtools log is pretty much empty. It shows even less than before as if the game didn't try to use the ffb. But the Wine log shows the correct...

> and winedebug with dinput and stuff > [winedbug_logffbGE.log](https://github.com/berarma/ffbtools/files/5814593/winedbug_logffbGE.log) This log seems to be incomplete. Can you post the whole file after having driving the car at least for some...

I was wrong, Wine doesn't have a SDL backend for DInput, it's only in the Wine fork used in Proton. From here we need some help from developers that know...

If you can build ProtonGE you can try a quick hack to see if the bug I've found makes a difference. Change this line: https://github.com/wine-mirror/wine/blob/e909986e6ea5ecd49b2b847f321ad89b2ae4f6f1/dlls/dinput/joystick_linuxinput.c#L564 From: `if (newDevice->joydev->has_ff && (i...

OK. When you do, building the Wine fork should be the same as building the original Wine. The README in the repository has directions. If the game worked on this...

There are some options to 'configure' command that can be useful. At least '--enable-win64' must be needed for 64 bit Wine.

> I didn't knew, that to get wheel support wee need proton. What about > wine-staging or wine-wine-tkg builds? I know they all requires SDL2, > but not sure if...

> EDIT2: For some reason using Proton-5.21-GE-1 works, but if I try normal proton or wine-valve this shows up: > 00f4:err:winediag:load_dxvk_config Couldn't load dxvk_config.dll, won't apply default DXVK config options...

Maybe the `ffbwrap` library isn't working correctly. It might be some thread bypassing the library. I think there's no way the queue can contain 7080 commands when using throttling.

> yeah i had older version. updated but, im still getting 20 commands to be delayed. > game is spamming them or whats the deal? i dunno how to check...