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

No FF with CSL elite and F1 esports wheel #19

Closed
DashieTM opened this issue Jan 3, 2022 · 5 comments
Closed

No FF with CSL elite and F1 esports wheel #19

DashieTM opened this issue Jan 3, 2022 · 5 comments

Comments

@DashieTM
Copy link

DashieTM commented Jan 3, 2022

Hello :)
First, thanks for the incredible work!
Please have some mercy, I am still new to the linux environment and I have no idea where else I should post this.

I am currently running a CSL Elite base alongside the F1 esports wheel and the csl elite pedals. (Pedals work flawlessly)
This combination results in strange FF behavior. Namely I only get speed wobble, curb rumble and off track effects, the regular FF doesn't seem to work. I currently tried F1 2020 and BeamNG drive.
The second game has some "FF" but it's behavior is extremely strange.
My guess is that the driver somehow can't access my wheel settings as my range is off as well.

I tried fiddling with the code to somehow force the driver to use 100% FF to see if that somehow does something but to no success. If you have any advice at all it would be appreciated.
If you need more info I will gladly provide, right now I have no Idea what else to post.

dmesg:
[ 2552.577314] usb 1-7: Product: FANATEC CSL Elite Wheel Base
[ 2552.577315] usb 1-7: Manufacturer: Fanatec
[ 2552.579231] hid_map_usage: 34 callbacks suppressed
[ 2552.579232] Fanatec FANATEC CSL Elite Wheel Base: Invalid code 768 type 1
[ 2552.579233] Fanatec FANATEC CSL Elite Wheel Base: Invalid code 769 type 1
[ 2552.579233] Fanatec FANATEC CSL Elite Wheel Base: Invalid code 770 type 1
[ 2552.579234] Fanatec FANATEC CSL Elite Wheel Base: Invalid code 771 type 1
[ 2552.579234] Fanatec FANATEC CSL Elite Wheel Base: Invalid code 772 type 1
[ 2552.579234] Fanatec FANATEC CSL Elite Wheel Base: Invalid code 773 type 1
[ 2552.579235] Fanatec FANATEC CSL Elite Wheel Base: Invalid code 774 type 1
[ 2552.579235] Fanatec FANATEC CSL Elite Wheel Base: Invalid code 775 type 1
[ 2552.579236] Fanatec FANATEC CSL Elite Wheel Base: Invalid code 776 type 1
[ 2552.579236] Fanatec FANATEC CSL Elite Wheel Base: Invalid code 777 type 1
[ 2552.579258] input: Fanatec FANATEC CSL Elite Wheel Base as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:0EB7:0E03.000D/input/input38
[ 2552.579389] hid-generic 0003:0EB7:0E03.000D: input,hidraw10: USB HID v1.11 Joystick [Fanatec FANATEC CSL Elite Wheel Base] on usb-0000:00:14.0-7/input0
[ 2552.645412] /home/dashie/gits/hid-fanatecff/hid-ftec.c: ftec_probe: ifnum 0
[ 2552.645479] input: Fanatec FANATEC CSL Elite Wheel Base as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:0EB7:0E03.000D/input/input39
[ 2552.697447] ftec_csl_elite 0003:0EB7:0E03.000D: input,hidraw10: USB HID v1.11 Joystick [Fanatec FANATEC CSL Elite Wheel Base] on usb-0000:00:14.0-7/input0
[ 2552.697450] /home/dashie/gits/hid-fanatecff/hid-ftec.c: ... 0 1 1 56
-128 127 -128 127

[ 2552.697451] /home/dashie/gits/hid-fanatecff/hid-ftecff.c: ... setting FF bits
[ 2552.697452] /home/dashie/gits/hid-fanatecff/hid-ftecff.c: setting range to 1080
[ 2552.697535] ftec_csl_elite 0003:0EB7:0E03.000D: Hires timer: period = 2 ms

image

Cheers.

@gotzl
Copy link
Owner

gotzl commented Jan 4, 2022

Hi,

I just tried F1 2020 for myself and I can confirm that the FFB is not working properly for me in this game as well. I started to dig around in wine/proton to see the FFB commands that are coming from the game, but so far they don't make too much sense for me... There seems to be no centering-forces and I wonder if it works with other wheels in Linux. With F1 2019 and the DFGT, I had a similar issue but was able to work around it by using the autocenter feature. I'll have to investigate some more.

A don't own BeamNG, so I can't say anything about that. You could create a log of the games FFB calls by setting "WINEDEBUG": "+dinput", in protons user_settings.py file. This might give me an idea what's going wrong ...

@DashieTM
Copy link
Author

DashieTM commented Jan 4, 2022

So sorry for the delay, I managed to record the calls, and it pretty much says everything -> "fixme"

36637.598:0124:02a0:fixme:dinput:IDirectInputDevice2WImpl_GetForceFeedbackState (0x79a0050)->(0x2335fc40): stub!
this about 100 million times.
I doubt this will be of any use but if there is anything else that i can provide don't hesitate to ask.

steam-1080110.log

@gotzl
Copy link
Owner

gotzl commented Jan 4, 2022

I actually was more interested in the the log for BeamNG. Still, looking at the log for F1, I'm missing a bunch of entries from dinput.. Could you verify that the entry in your user_settings.py is correct? And then maybe attach the log for BeamNG? The log should be cluttered with *:trace:dinput:fill_DataFormat Copying* and occasionally lines looking like *:trace:dinput:_dump_DI*, the latter are the ones I'm after ;)

@DashieTM
Copy link
Author

DashieTM commented Jan 4, 2022

Forgot to rename the file. I figured that out once I had just +dinput in there.
The whole files were too large so these are snippets, but it should do the trick.
F12020.log
BeamNG.log

@gotzl
Copy link
Owner

gotzl commented Feb 5, 2022

I've created #22 and #23 since these issues happen with all devices.

@gotzl gotzl closed this as completed Feb 5, 2022
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

2 participants