Hi

In LFS I can normally have smooth animated multiplayer racing (and that's the only realistic racing anyway in my opinion) without the slightest dropouts.

Anything else, content, graphics, tire model, damage model, you name it, doesn't interest me in the slightest way, as long as it is programmed in a manner which I can call realistic. This is fulfilled in LFS and it gets better.

Bottom line: The main aspects of a good race, in my opinion, are not perfectly designed graphics, highly diverse or licensed cars and tracks or a absolutely perfect physics engine. It's a bunch of good, partly cold blooded, partly hot headed, racers who don't give anything about a perfectly modeled engine sound.

It's about racing. I can do this here.

Greets,
JPursey

Hooray,

turning off APIC for my system solved the problem for me. The last three times I connected there was no lag issue anymore.

This included reconfiguring my system from APIC to "Standard PC", however, which costed me some sweat.

From what I read on the internet (www.planet3dnow.de seems to be an interesting source, for example) it may be that on older nForce2-Platforms (which mine is) the APIC feature isn't implemented very well. Switching my system made it possible to switch APIC off. Now the lag is gone.

On the other hand, the reconfiguring procedures Windows did after switching scared me a lot and there seem to be little issues with my floppy and harddisk driver, but the system works.

By the way: Does anybody know how to permanently deinstall the floppy driver when windows reinstalls it at every bootup, although it's deactivated BIOS-wise? Thank you.

I'm happy again.

Greets,
JP

Last edited by Jimmy Pursey, Tue, 20 Feb 2007 10:50.

Hello,

although this doesn't seem to get much interest (however, it should in my opinion) I thought I'd post my latest observations:

In the past time I did some checks everytime I booted my machine and played LFS.

Everytime I boot the system clock (the BIOS clock) runs at correct speed compaired to my watch.

In many cases (today 100% out of about 5 boots) the windows clock will run faster about 1 second per minute. This always results into the stuttering lag phenomenon.

The stuttering lag has different intensities with no observable tendencies. Whether it is proportional to the grade of acceleration of the clock I cannot say due to missing measurement equipment.

Developers, can you please state your opinion regarding this case? What may cause the windows clock running so fast?

Greets,
J.P.

Mercedes Benz 300SL

Hello,

I am experiencing the same problems as Dani King shows in his screenshot and have similar messages when F8 pressed.

This problem occurs randomly and can sometimes be "fixed" by rebooting my machine a few times.

I also noticed that sometimes my LFS client seems to run too fast, that is, when comparing the time elapsed in a hotlap to the time elapsed on my watch, LFS displays more time elapsed than my watch.

So I guess that the stuttering lag happening to me AND the "fast client phenomenon" could be caused by my system clock running too fast. This could cause my machine to run out of sync with the host machine, thus causing the LFS client to try a synchronisation resulting in connenction hickups and those strange messages.

What do you think?

Greets,
J.P.

I don't know if this helps you with your problem because I can't figure whether your symptoms fit to mine, but anyway:

When driving with my Logitech MOMO red I realized that in some cases it appeared to be more sensitive in LFS and after sharp turns it was biased to one side. The centering seemed to be jerked.

It took a while until I found out what happened: When starting LFS (or even Windows, but it doesn't make a difference because I use it only for LFS) the maximum turn angles for maximum output were less than the mechanically possible turn angles. This means that the wheel was not calibrated properly and recalibration of an axis took place once the axis was moved beyond the maximum output turn angle. Then the center point also moved and the wheel appeared to be tilted.

Workaround: Either in the profiler or in the Options-->Controls window in LFS (where you can see the axis outputs) move ALL axises to full angle once, thus calibrating the wheel. This fixed my problem.

I can't say if this helps with the problems mentioned here, especially because most of you speak of the MOMO black, but who knows?

I vote for:


+ Tire preheating system

+ Start from the pits

+ HLVC indicates "invalid" for going backwards

Would you mind to describe how you set up such a widescreen in the ATI driver's menue? As far as I know the ATI driver doesn't support what is called "horizontal span" at NVidia. I would like to try a dual head setup with my 9800pro too, that's why I ask.

Also, what resolution do you use in LFS?

Kind of same problem here.


It says I have a +30 sec distance to benchmark on blgp rev in FZ 50 GTR.

But I doubt it is possible to get a time below 40 secs on this track/car-combo.
Also, I can't find anybody who uploaded such a hotlap. Fastest Racer is biggie and although his time seems to be just as unreacheable for me I believe he uploaded a correct replay.

Unfortunately... :-)

You just have to make sure that the utility that comes with the driver (i.e. nview) stretches it across both monitors, iirc.


That would be the "horizontal span" that NVidia drivers provide, right?

Now if I activated this with my potential NVidia card (unfortunately I run on ATI atm) wouldn't that interfere with the resolutions I choose in LFS, leading to a horizontally overstretched image (since there are no 8:3 or even 32:9 resolutions in LFS)?

In other words: Wouldn't it be that LFS must provide at least a 8:3 viewport to get an undistorted view across 2 4:3 displays?

Since we already have the FOV task here and I couldn't find anything about this topic elsewhere:

Does anybody know if there are plans to make LFS support dual head setups for NVidia and ATI cards?

Or: does anybody know about how to get LFS to work with a dual head setup?