Did you install latest lfs version which is 0.7E?

Awesome work on moding this iconic car, tnx man. Also, tnx very much for documenting the process.

Quote from Bandit77 :

Maybe one could kind of stretch the area of the bite point that way, but it's probably not worth the hassle.

Yes, that would be doable, it's a good idea. You can play around and make the curve such that it's almost flat at the top, with a very small angle between horizontal line and then a bigger angle down to 0 input. The break point (center) could be somewhat before the actual central value of input. If you are very keen on doing a real life smooth start, some trial and error is required untill you nail the curve.

Note that axis clutch in lfs is saturated completely (fully open clutch) for about 70% of axis input, so take that into consideration when playing with DXtweak axis calibration.

Last edited by rane_nbg, Mon 11 Mar 2024, 18:50.

Well, the bite point of clutch is known to be very small in lfs. One has to be very precise, so 8bit (logitech) pedals will not cut it. With 10bits like the ones from thrustmaster, it's a little bit easier, but still quite challenging.

We did mention this to Scawen, but for bikes. I wouldn't worry about it too much before a new tire physics is released. Then we can go nuts with all kinds of requests

With the correct actuation of the manual axis clutch, it is possible to have a very smooth launch. I agree, it's not easy at all

Very nice layout and perfect driving. It was very intense to watch, tnx man

Beautiful car, and awesome job with the modeling, tnx man.

How about, asking the mod creator directly to implement those tweaks?

/spectimeout

No, it was not fanaleds, it's too complex for the lfs. I was something like G27 leds program, but I can check later.

Yeah, I think good solution would be a text command to set this timeout in server side. Default timeout should be in the order of magnitude of 1 lap, so 4min sounds reasonable.

You have to debug your code to see where the problem is. Without posting what you have so far and what is inside of this txt file, it's impossible to help further.

You have to put a limit such that $CurrPage is never negative (or less than 1) which ever is the starting value, it must not be less than starting value. But as I see, this limiter is already there, so there should be no problem. What kind of problem do you observe when pressing page back button?

Last edited by rane_nbg, Wed 6 Mar 2024, 14:04.

Hi, yes I got them working using some third-party thing. In the end, I turned it off because it causes FFB to sometimes lag behind.

I forgot what was the name of program and where I got it, but I could look it up and send it to you after 22nd march.

Then your best bet is to wait for some lapper guru to comment.

Yes, you will have to use some sort of for loop, that goes through the text lines.

This doesn't seems like a scroll bar as you would see in windows for example. I think it's just a manual trick, that shows certain number of lines of text. Pressing up and down button just itterates through the array, or some index.

What about spinners and rotators? I'm not sure if it is possible to put a rotator on the steering wheel and have it locked to its coordinates though.

Well, this sums it up perfectly for me:

"Crap, I'm an adult now."

Exactly, I'd rather they spend their time on updating LFS, then on making fancy reports. Progress reports with pictures are a luxury at the moment.

I beleive this is the fault of the speed limiter routine in LFS.

If it doesn't have already, it should have a PID loop. It may also be that it is simply not reacting fast enough. Scawen needs to retune some parameters for it. It has 3 terms, proportional, integral and differential. Most probably integral needs incresing a little bit.

It's like writting a letter to someone in the good old days. You wait, a reply letter may come or it may not. That's the fun

Or yes, dig a little bit more in this forum. It seems we already disscused about this, I forgot already

Then I suggest to lookup how to create a substring that removes all characters after decimal point, including the point. I don't know what programing language lapper uses, try to dig that out then google how to do substrings in it.

Do you need to round the number to the nearest integer, or you just do not want to display any digits after a decimal point, when showing it on screen?

I'm guessing there is a way to cast float into an integer, or to use some stardard string formating procedure to create a substring which has no digits after a decimal point.