Bernat
Bernat
> There is no point in being correct if no one wants to do it that way. But even before everything, a small scale test can be done to see...
So the reason is that it's easier to just let the firmware do whatever it does. Thus you'd really want the API to be open about it and not force...
How does it self describe?
> which self describes that my wheel have 900° rotation range Sorry, I meant this. How could I detect the rotation range?
Based on the description provided, and the hardware features, I could add a sensitivity option that does nothing. :)
It could be that some other application is using the device. Are you sure it wasn't being used when you tried the test? The Flatpak version has just been released...
> I tested it initially when I was working on the flatpak, but haven't since. I tested it now and I believe https://github.com/berarma/oversteer/pull/197 is affecting the application with with newer...
I've tried the Flatpak version and the test works. I haven't run it fully but it starts. If the FFB doesn't work anywhere, it's probably because there's some issue in...
For compatibility reasons, Oversteer only supports a set of devices listed in the README. You might have everything correctly setup but your wheel isn't in the list.
Please, can you post the USB vendor/product id displayed with the command `lsusb`? Have you installed `hid-tmff2`? I'm guessing that wheel can have more than one id and the driver...