Open HardTy opened 1 month ago
Yes... Unfortunately looks like reading out wheel-id needs more work .. I wonder why it's only 0x00
for you. Does it keep that value even after you've turned the wheel?
Yes, it keeps the same value.
I can confirm wheel_id only displays 0x00
whatever wheel is mounted on my Clubsport v2.5 base
I have the same issue, only displays 0x00.. if I cycle trough csw mode back to PC mode, it shows 0x04 for sometimes a couple of seconds to some minutes, then it goes back to 0x00.
Fixed the fantec led server temporarily for me by hard coding the wheel code into it, otherwise it throws a key value error "00"
How can I try the hidraw branch ? Any tutorial on patching proton so it can talk to the wheel ?
Ps: also the wheel goes wild pressing all buttons mapped to the wheel when I change something in the tuning menu, resulting in me teleporting to pits and honking until I press the honk again.
I'm not sure if this is the right place here. I tried to get gotzl/hid-fanatecff-tools running but got the following trace:
I did some testing and found out that I get a wrong/no ID when I print the
wheel_id
in sysfs.I fixed the problem by changing https://github.com/gotzl/hid-fanatecff-tools/blob/master/dbus/fanatec_input.py#L24, but that doesn't seem to be the right way. :)
I am using the latest git tag gotzl/hid-fanatecff:0.1.1