Do not listen to this young guy

You have come to the perfect place. LFS is a great and affordable sim, with plenty of good cars and tracks. The community is small but also very fun and helpufull.

As pricing is concerned, there are different licenses demo (free), S1, S2 and S3. One can buy one by one and upgrade. Have a look here for exact prices https://www.lfs.net/shop

For start you can try demo for free, then if you like it, no more that up to S2 is really needed. S2 should be no more than 30 dollars I guess, for USA. It's a one time payment, no iRenting bs.

Last edited by rane_nbg, Thu 8 Apr 2021, 10:13.

There is a mouse sensitivity option in version 6V. Options/controls/axes then under available axes you can adjust mouse X and Y sens. It starts from 0.5 and maxes out at 20, with a step of 0.1

If that is not enough range for you, you can always change windows mouse sensitivity.

PS. I just realized that yesterday was 10 full years since I joined this forum and had a total of 10 posts

Last edited by rane_nbg, Tue 6 Apr 2021, 20:42.

In principle, everything looks good from the PID side I would say. There is a limit anyway in the granularity of the DirectX input of 10000. That is why instead of full 16bit values (+-32k, or 65k) they have put 10000 instead, that is all fine. Logical and physical values are reported and defined correctly. As I mentioned before, there is still a lot of processing done with those values before they get sent out to motor as some PWM driving signals. But it is fishy how other games run fine. This is very interesting since I did have kind of similar problems while developing my own firmware for an Arduino based FFB wheel. Without WheelCheck I would have not been able to scale effects and calculate forces correctly, it was a great help for troubleshooting FFB issues.

Have you tried playing with the wheel with force (PID) effect? Does it work correctly or you have it the same as in LFS? Try also those effects at the bottom, inertia, friction or damper. There is an offset for these effects, this will shift the X-axis range, but it is only for the WheelCheck program, see if that makes any difference. It might at least give us an idea of where the problem is. Before pinpointing the issue, I can not say for sure if the problem is in their firmware or elsewhere.

Maybe we can get on discord some time and try to do some tests in WheelCheck together.

Last edited by rane_nbg, Sun 4 Apr 2021, 05:50.

Tnx for this, it's a good idea.
How to make it work in windows?

At this point, I'm afraid that you are only left with some diagnostics tools. Most probably, the fix needs to be in the firmware of the device itself. More accurately PID (physical interface device) part of the HID (human interface device) descriptor.

WheelCheck is really a great program. It was made by guys from iRacing. It can read device HID definitions, as well as PID - FFB effect definitions. You can basically see everything that is in the firmware of the device regarding FFB. Additionally, you can apply some FFB effects like a constant force to test your device. The only FFB effect LFS uses is constant force - it sends FF rate times per second a constant value of force to the wheel in the range of 0 to FF steps, giving the illusion of time-dependent force. How these values are then scaled to the signal which is sent to the motors is another part. Here you can only see the logical or software side of things, done by Microsoft in 1999.

Have a look at some of my print screens for where to look for important FFB things.

You can recalibrate the axis in the DXView2 only. I would still try to check it with WheelCheck, put some spring force, and see if that works normally. If not, then it has to do something with the firmware of the wheel, which you can do nothing about. And about the wheel being reported by Windows as joystick or wheel, does not matter for LFS. If you can not find it, pm me, I can send you the exe file.

Did you try to set in LFS (patch V) options/controls/axis FF steps to 10000 and FF rate to 100Hz, turn of dead zone?

You need to install the drivers for FFB to work properly, just look for the version prior to G hub.

Last edited by rane_nbg, Fri 2 Apr 2021, 19:59.

Hi, I would warmly recommend uninstalling G Hub, since it does your wheel no good. It is suited for mice, keyboards, and headphones with RGB lighting mostly. It has absolutely no available settings for the wheel itself.

Previous versions of drivers are much much better. I have G29 and I tried G Hub when it came out. I was happy that there was an update, but only for a short time. I got instantly disappointed in how crappy it is for the wheel and the lack of any settings the previous version had. Do not be fooled with new looks, there is nothing new in it for the G29/G920 in the firmware or FFB side of things.

I've heard from some guys who installed it that they even completely lost FFB in LFS.

This sounds like a standard problem with wrongly choosing a signed or unsigned integer, which simply gets overflown.

example: a) int16_t, 16bit, -32767 to 32767 (0 center)
b) uint16_t, 16bit, 0 to 65535 (32768 center)

This is defined in the HID, or firmware of the device. Usually for wheel controllers, the steering axis is a signed integer, for example (a), where the raw value of 0 is a wheel center and this is used to calculate the FFB. In that case, bits 0 to 14 are the value, while the last bit15 is a sign. Giving this variable a value of 32768 will cause it to overflow and give a result of -32767. The same goes for an FFB magnitude value, which if not defined correctly may cause the same issue. The LFS is simply reading whatever is reported by the device in HID descriptor.

To check this, I would suggest you try one of the following programs capable of reading raw values from USB joysticks or wheels: DIView, DXTweak2
The best would be: WheelCheck which can generate FFB effects as well.

See attached pictures of DXTweak. For some reason, I got device names reversed while printscreen. My DIY Arduino wheel is -32k to 32k and Thrustmaster wheel is 0 65535 in X axis. Both wheels are working normally in LFS with the correct FFB.

Last edited by rane_nbg, Fri 2 Apr 2021, 11:18.

LFSW name: rane_nbg
In-game name: AA™| rane
Full team name: Air Attack
Nation: Serbia

LFSW name: rane_nbg
In-game name: AA™| rane
Full team name: AirAttack
Nation: Serbia