Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Range Change #7

Closed
dafteran4 opened this issue Nov 13, 2020 · 3 comments
Closed

Range Change #7

dafteran4 opened this issue Nov 13, 2020 · 3 comments

Comments

@dafteran4
Copy link

dafteran4 commented Nov 13, 2020

In the README, there are instructions on how to change range by writing to file:
/sys/bus/devices/XXXX:044F:B66E.XXX/range

In my system (Arch Linux) there is no such file, instead the range can be changed at:
/sys/devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/0003:044F:B66E.0008/range

The exact path varies and can be seen in dmesg when plugging-in the wheel.

The driver seems to init 900 degrees range, aren't TM3000RS wheels all 1080?

Btw, I've been testing the wheel in Dirt Rally and BeamNG and it works great.

@Kimplul
Copy link
Owner

Kimplul commented Nov 13, 2020

Seems like I have a typo, the path should be /sys/bus/hid/devices, good catch.

Yep, all TM wheels that I know of support 1080 degrees, but Oversteer seems to at the moment only go up to 900, which is what I set the default to. I can maybe open up a patch for 1080 support for TM in Oversteer, I'll see.

Good to hear that the driver works.

@dafteran4
Copy link
Author

dafteran4 commented Nov 13, 2020

Seems like I have a typo, the path should be /sys/bus/hid/devices, good catch.

Ah, that's shorter and more practical. Thanks.

@berarma
Copy link

berarma commented Nov 14, 2020

Ah, that's shorter and more practical. Thanks.

It doesn't look shorter, it's actually longer.

Yep, all TM wheels that I know of support 1080 degrees, but Oversteer seems to at the moment only go up to 900, which is what I set the default to. I can maybe open up a patch for 1080 support for TM in Oversteer, I'll see.

Feel free to open an issue for it and I'll work on it when I can. Implementing device dependent ranges is on my todo list, but I didn't notice it was important for TM support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants