Hello,

i am having difficulties to get Force Feedback running for my G27.

I am running an unmodified 3.3.6 Kernel and use the following udev rule


After attaching the G27 i get the following output ( using dmesg)


In /dev/input/G27event is created and linked to /dev/bus/usb/001/009

When i try to thest FF with fftest, i get


Is anyone using FF with the G27 and a similar configuration?
Any idea why fftest failes?

Regards, and Thank you
Manuel

As of kernel 3.2 you should not need LTWC at all. The wheel should switch to the native mode automatically when it's connected and your dmesg log suggests that it really happens.

I can't test this at the moment, but because of the way LTWC sets the wheel up, it's possible that it's fighting with the kernel driver over the wheel which leads to an invalid /dev/input/G27event entry.

I suggest you try this: Remove the LTWC entry from udev rules, plug the wheel in, let it calibrate, run

(the "xxxx" value might change, you can read the current value from dmesg)
and try the fftest again.

I made a stupid mistake and was trying to test FF with the wrong event (device?)

After running

cat /proc/bus/input/devices

i saw that /dev/input/event15 is the right event handler for the attached Wheel. Running fftest on event15 works just fine.

I thought the udev rule was supposed to generate a link to the current event handler.

Regards,
Manuel

Quote from mapa17 :

I thought the udev rule was supposed to generate a link to the current event handler.

That's my understanding of it too, however, there's a catch. LTWC literally takes the G27 away from the kernel's control, does stuff with it and then returns it back. Logitech wheels are handled "properly" since kernel 3.2, so when the kernel gets the wheel back, it reinitializes it again which leads to new /dev/input entries being created. Perhaps that somehow confuses udev so the link it creates points to the old invalid entry.

Does it work when you remove the LTWC part from your udev rules?

FWIW, this is how I start LFS with the g27 under wine. Just set the RANGE to whatever you want and you should be golden, unless you're using 2 g27s at the same time

Hi to all,
I'm an arch linux user (64 bit) and I'm restarting gaming with Grand Prix Legend and Live for speed with wine.
I would like to buy a better steering wheel compared with my trust GM3200 one (which has combined pedals and no Force Feddback).
What is the best and fully functional one I can find?
It seem to me that G25/G27 work well with LTWheelConf. Is it correct?Is there any cheaper wheel which I can consider?Thank you,
Xwang

As an Arch Linux user you have the latest kernel 3.5 available (unless you're using some -lts version). Kernel 3.2 and above have support for Logitech gaming wheels (DFP, DFGT, G2x), kernel 3.5 even supports the LEDs on G27. If you're running such a kernel, you should not need LTWC anymore. If you run into any trouble, feel free to post it here...

Quote from MadCatX :

As an Arch Linux user you have the latest kernel 3.5 available (unless you're using some -lts version). Kernel 3.2 and above have support for Logitech gaming wheels (DFP, DFGT, G2x), kernel 3.5 even supports the LEDs on G27. If you're running such a kernel, you should not need LTWC anymore. If you run into any trouble, feel free to post it here...

Wow perfect!
Today I've seen in a shop a Logitech Driving force GT sold at 139.98€
Since the G27 costs in the same shop the double, I think I will choose the DFGT.
So you can confirm me that it is perfectly recognised on linux and wine (separated pedals, 900° and force feedback).
Can someone, who has the DGFT and linux, test if Grand Prix Legends recognises it correctly?
Thank you,
Xwang

PS is DFGT a good choice or it is better to invest more money and buy the G27?

I don't have any first hand experience with DFGT, but all the bits are there in the driver, so at least the native mode and FFB should work out of the box. I'm not sure about the separated pedals. I'd have to take a look at DFGT's HID descriptor, but even if it doesn't work right away, it should be fairly possible to fix it with a simple kernel patch.
Unfortunately I can't comment on GPL, but we've had no problems with WINE or games picking the tested wheels up.

Quote from MadCatX :

I don't have any first hand experience with DFGT, but all the bits are there in the driver, so at least the native mode and FFB should work out of the box. I'm not sure about the separated pedals. I'd have to take a look at DFGT's HID descriptor, but even if it doesn't work right away, it should be fairly possible to fix it with a simple kernel patch.
Unfortunately I can't comment on GPL, but we've had no problems with WINE or games picking the tested wheels up.

Ok thank you for your help.
I'm still thinking if it is better for me to buy the DFGT or if I should buy the G27 (which has the clutch and the H shift which I don't know if is recognized in GPL under wine).
Maybe I can search for a used G27.
Xwang

I have both the DFGT and the G27 and run Arch on both computers. Both wheels work great and have force feedback support. I love my G27 but the DFGT works great for half the money (here in the USA).

If you have driven with a wheel and know that you love it, get the G27. If you're not sure, or don't have the money to spend, get the DFGT; it's good enough and not that expensive. Well, at least for the people where I live.

PS: I use the script I posted above to set the range I want, though I use 270 rather than 180 now.

Quote from rowdog :

I have both the DFGT and the G27 and run Arch on both computers. Both wheels work great and have force feedback support. I love my G27 but the DFGT works great for half the money (here in the USA).

If you have driven with a wheel and know that you love it, get the G27. If you're not sure, or don't have the money to spend, get the DFGT; it's good enough and not that expensive. Well, at least for the people where I live.

PS: I use the script I posted above to set the range I want, though I use 270 rather than 180 now.

Thank you for reporting your experience.
I've read on the net that the biggest difference between the two steering wheel is the feeling of pedals. More in detail the G27 are perfect while DFGT are too soft. Moreover G27 has the clutch pedal and the H gear shifter.
Since I've already used a low price wheel (no feedback and only combined brake and accelerator pedals), I'm wondering if it is the case to buy directly the G27 considering that Grand Prix Legend simulates the 1967 F1 season in which the use of manual H shift gear with cluth should give more realism.
Is it right?
Xwang

Xwang, yes, you have it right. For what it's worth, I highly recommend the G27 as I prefer leather and steel over plastic and foam rubber.

Hi,

Have just discovered this thread and am blown away by the progress you've made hacking these devices. Well done to you all. Unfortunately though I'm still stuck at the start line..

ltwheelconf -l gives 'Found 0 devices'

I've confirmed the wheel works with evtest and have been using it on Toca Race Driver 3 (through latest Wine). I just wanted to get it centering and adjust the wheel weight.

Plugging in the device gives:

cat /proc/bus/input/devices:

lsusb:

evtest:

Have tried using ltwheelconf -d with various addresses and ID numbers but to no avail. Any help appreciated, please ask if you need any other info..

Thanks in advance.

System info:
Ubuntu 12.04 LTS 32bit
Dell 1720 laptop.
Intel® Core™2 Duo CPU T7500 @ 2.20GHz
NVIDIA Geforce 8600 m gt

Silly me.

sudo ltwheelconf -l:

D'oh

Dose anyone know got to set up the force feedback for DFGT?

DFGT should be supported natively by the kernel. Unless you're running a very old distro, it should work out of the box. If it doesn't, please post more detailed description of the problem you're having.

I'm using Ubuntu 14.04 uptodate the only problem is that I'm not getting any force feedback at all, The game I'm using to text the force feedback is Euro Trick Sim 2.

commands used to set this up.

sudo ltwheelconf --wheel DFGT --nativemode --range 900 -- autocenter 25 --rampspeed 7

sudo ltwheelconf --wheel DFGT --device /dev/input/even0 --gain 100 altautocenter 100

As far as i know ETS2 doesn't have Force Feedback (at least not for me).

LTWheelConf should not be needed at all. In fact, because the entire FFB support has been moved into the kernel, LTWheelConf cannot work properly anymore. You should be able to set the range via the kernel interface by writing the desired range into

.

Are you sure that the device appears as "event0" in /dev/input? You can find out the correct node name from dmesg. Are you getting force feedback in other games?

ETS2 makes use of effects that are not supported in current kernel drivers. A series of out-of-tree patches that enable full support exists, but you'd have to build yourself a customized kernel.

Heres what I found after doing dmesg and as for testing it on other game no because I don't have any other racing/driver sims that work on Ubuntu. (I've only been using Ubuntu for about a week)

The wheel seems to be picked up properly by the kernel so you should have force feedback in games that use "constant force" effect. I don't have a first hand experience with ETS2 but as far as I know it mostly uses "damper" and "spring" effects which are unsupported by the driver present in the Ubuntu 14.04 kernel...

So I'd have to make my own driver for ETS2?

You'd have to patch the kernel with some improvements that have not made in into the official Linux kernel yet. It's not particularly difficult to do but you should look up some tutorials how to build a custom kernel in Ubuntu before you try...

FWIW, the patched lg4ff driver and the additional stuff that's required for it to work can be found here (https://github.com/edwin-v/linux-hid-lg4ff-next).

Quote from MadCatX :

LTWheelConf should not be needed at all. In fact, because the entire FFB support has been moved into the kernel, LTWheelConf cannot work properly anymore. You should be able to set the range via the kernel interface by writing the desired range into


/sys/module/hid_logitech/drivers/hid:logitech/*:*/range


.

*Hijack*

Yeah, setting range to <whatever> seems to work, but how do you set the actual force feedback? For example, when running over a rumble strip in Windows I get feedback in the wheel, but in Linux it's completely dead. Perhaps this is not supported?

(I also, in desperation tried [...] --gain 100 --device /dev/input/event23, but that didn't help.)

In case this is of any relevance: