This wheel should be working perfectly since LFS and most other racing games are using Direct Input API for FFB effects developed by Microsoft in 1999.

Personally, for logitech G29 I use 900 degrees in wheel driver in windows. In LFS I set wheel turn to 880 and wheel turn compensation to 1.0, that way it was perfect while the GTi cars had 720 deg of steering. Now the animation is changed to 1080 and you are no longer able to set 1:1 your wheel with respect to ingame wheel.

But try this, 900deg in driver, in LFS wheel turn 900 and compensation 0.

Unfortunately, there is nothing you can do to remove that huge firmware steering dead zone around the center. There is an option in LFS called remove dead zone, but I am not sure if it will do anything, you may try it.

The dead zone is there because the wheel is centered back with some springy rope or something. Due to friction, it does not always go back to the exact center and this software dead zone makes sure that a large centering uncertainty gets registered as a wheel center position. This wheel is not made for games like LFS, it is more like for arcade titles, where you pretty much do not even need to steer and the car will keep going somehow.

Entertaining thread indeed, haha

I'm using G27leds software on my G29 and LEDs do work good. However, I do not recommend using it because it is replacing an important dll file responsible for direct input. I have noticed some funny behavior of FFB and even some weird FFB latencies which are not there if I do not use it. I was not able to make it work with Fanaled, but I admit I did not spend much time troubleshooting it.

LFS has an updated resolution of FFB that will use the full potential of direct input API. Any FFB wheel will benefit from that, especially DD.

There is just one slight downside with LFS. For some DIY wheels, LFS is only sending a one-sided FFB, but this problem should not occur with Fanatec wheels - I hope.

very nice layout, great job dude

Very interesting read indeed, tnx.

I was always wondering why this offset is so huge on go-carts, it really makes it hard to steer. However, in LFS FWD cars like XFG or FXO I never noticed this torque steering behavior, I guess it is a very subtle FFB effect and I just got used to it. Buy now, it is my muscle memory for cars behavior and probably I am not able to even try and imagine what driving would feel like with a shorter wheel center offset.

Another update, I tested openFFB firmware on stm32F407 microcontroller.

I could replicate the same issue by selecting only 1 FFB axis in their configurator. LFS would only send one-sided FFB. If however, I set 2 FFB axis, LFS had no problems with that and FFB was correct, with both sides. Seems quite opposite to what I have in my Arduino FFB firmware, but it does not matter. I guess that this pinpoints the issue for developers of both FFB wheels and LFS.

It does sound like a nice idea, no pun intended. But it may create a lot of unnecessary complexity in the net code, which is really not needed.

What happens if you want to download a replay? One would need to download additional stuff just for the sound parameters. During a race, one would need to constantly send and receive all this data from all connected players. I see lags, problems.. I do hope I am wrong about this.

Last edited by rane_nbg, Wed 18 Aug 2021, 09:27.

Guys, before you get carried away too much, just appreciate what is already there in the sim. It looks like Pajkul is the only one who realizes how much work is required for these giant requests. It just ain't never gonna happen if Scawen continues to do things alone.

But, if I could choose only one of all here mentioned updates for LFS, it would definitely be Jessica Alba

Seriously, my only request is ingame real time FFB monitor and min force FFB slider. These are very easy and quick to implement and it's a pitty that they are not already in the game.

Last edited by rane_nbg, Wed 18 Aug 2021, 09:16.

It really needs to be done in the PID descriptor part of the firmware, which defines the number of FFB axis and other properties. If VRS guys didn't make this configurable, there is nothing you can do from the outside.

A good example of this is done by guys that are developing openFFB firmware, where you can select up to 3 FFB axes from their configurator software. Maybe in the future, they are able to reconfigure their firmware for wiring to be the same as in mmos, then you would be able to just upload openFFB firmware in your hardware and have it working.

https://hackaday.io/project/163904-open-ffboard
https://github.com/Ultrawipf/OpenFFBoard

Quote from NumberTwo :

yeah i dont care much about all you said

hahaha you know how to be brutal for sure.

I agree with you, the look and feel of LFS is only a small part of the enjoyment. Everything else is what makes it much better. Sometimes I wonder if we had more players, would it still be the same, or would it just eventually end up being the same as every other sim. Having a small community that is unique and quite filtered out from crap players is what makes this sim great as well.

Hi guys, after some time, I think I was able to replicate this issue on my homemade Arduino FFB wheel firmware.

The same behavior is happening if I enable 2 FFB axes (X and Y) in my firmware. LFS is only sending negative values of FFB, there are no positive values. However, if I reconfigure my firmware to only have 1 FFB axis (X only) all is fine.

The weirdest thing is that my Thrustmaster T300RS has 2 FFB axes defined in its firmware and it still works normally in LFS.

I do not know if this will help anyone but I just wanted to share my findings.

Well yes, the same cars can surely have different speeds and braking capabilities - it is called a car setup.

As others already pointed out, make sure that you can press your pedals fully and that it is registered in lfs as a full excitation of a corresponding axis.

You can always upgrade a graphics card at a later point. It seems like a good deal, it will run LFS just fine. Just make sure to install it on the SSD.

You are absolutely right. I'm positive that devs will fix this, it is only a minor issue, that should be not too much time-consuming.

I am using the original spring with a pencil eraser, I found the one with a similar profile, but it was longer, I just cut it down to a similar size. It is softer than the stock G29 rubber bar and it's much better for me. I have more room for modulation as it gets squeezed hard.

It's most probably an issue with the drivers. That error appears if the device reports 2 FFB axis, LFS only uses 1 and is not able to create FFB effects for the other one.

You need to figure out which version of drivers will work with lfs.

You can always have a go with port forwarding. Google it for your router.

When you start lfs setup exe run it as an administrator.

Very nice work man.

I will not be of any help, since I do not know how to set up a drift server. We use airio which configures LFS through inSim on our servers and it is not able to support drifting stuff.

Not sure about vertical FOV, but I use 82deg horizontal FOV on Oculus CV1.

If you do trial and error, what seems to be an ok value?

In order to connect to an LFS server as an admin, you just need to enter the server admin password prior to joining the server. Then the above-mentioned commands will be available.