On Fri Aug 8 21:48:51 2025 +0000, Tomasz Pakuła wrote:
Nothing is broken, the autocenter is just left to the drivers. The autocenter philosphy is very different on Linux vs windows where Setting an autocenter effect outside of the main program is a valid use-case. Linux doesn't even have a notion of acquiring FFB devices and you're free to send in effects from different. Yes, this change fixes the behavior of a lot of ffb devices for a lot of users, as can be seen here: https://github.com/ValveSoftware/Proton/issues/8395 Until we have a better Linux ffb api that's closer to the functionality of full PID protocol/dinput ffb api this is the best compromise. If you truly, really, just have to have autocenter on reset without using hidraw, please make an issue in the `hid-universal-pidff` development repository and we could upstream it. We're already tracking the number of effects and we could enable autocenter when there are none.
@TomaszPakula we are not on the same page. You are focused on particular programs and devices. Under Windows they had autocenter off. Under Wine they had autocenter on. You fixed this by removing `DIPROP_AUTOCENTER` support from the udev input and SDL backends. The programs now work with the devices as under Windows so you say nothing was broken.
I understand that. It isn't my perspective though. I put a lot of work into making `DIPROP_AUTOCENTER` work for all the backends. I want to fix whatever is wrong with it in the udev input and SDL backends for your programs and input devices rather than rip it out. If I can do this, then we all win, and Wine becomes that much better, so please give me a chance.
To that end, could you please run the [test program](https://github.com/twhitehead/issue-wine-ff-autocenter) with a version of Wine before the merge request was included, as well as under Windows, and report back what happens for you device. Thank you!