Quote from PoVo :

Yes if you're a demo player.

Incorrect presumption award goes to....

Quote from MadCatX :

Well, we only got largely improved layout editor with new objects and stuff, free roam mode (something cruisers've been moaning for for years), fixed collision detection model (something everybody's been longing for for years), InSim updates, graphics engine optimizations and fixes for a couple of annoying bugs, I can see how some people don't consider it a patch...

*Giggles* .. ok, easy satisfied I see! It's still the same LFS is was 3 years ago, but now you can drive off track! Woohoo!! You must make it very easy work for the GF, being so easily satisfied

Now back to fixing the Tardis!

Quote from PoVo :

There's no idiocy in his post. Besides you're a demo player - don't argue with S2'ers or you'll get a few forum whores attacking your bum

Oh I'm a demo player? Nice presumption And the idiocy IS beyond words (sorry for late replay, I had to do a call out repair to the Mars Rover)

Quote from MadCatX :

Was this some form of sarcasm I didn't understand or do you people happen to have missed the last patch released in June?

Hahahahahahahahahahaha, you call that a patch?! (sorry for late replay, I was repairing the Tardis)

Quote from stumbi :

Never. Sadly, LFS is a dead game which is not developed any more.

This tool speaketh the truth

Quote from cargame.nl :

Actually, yes.

Amount of control, InSim stuff.. Its not matchable by any other sim.

The idiocy in this post is beyond words for me....

Quote from JasonJ :

7,700 race laps (+many practice laps), never once timed out from US or AUS servers.
You can keep track of your internet conn in the FPS indicator (F key)
L=Latency
Q=quality
S=Sync? (I forget now)

**Taken from the Nascar Racing 2003 Readme (same thing for iRacing)

(L) Instantaneous latency from 0.0 seconds (the bar is empty) to 1.0 seconds (the bar is full height). This is the amount of time that it takes for a message to go from the server, to your client, and back to the server.

(Q) Quality from 100% (the bar is empty) to 50% (the bar is full height). The more data that is lost or garbled during transmission from the server to you, the lower the quality of your connection, and the higher this bar will go.

(S) The time skew (difference) between your client and the server. If your current time is behind where you expect the server to be, this bar will be below center. If it is at the bottom, then you believe that you are 1.0 seconds (or more) behind the server. If your current time is ahead of where you expect the server to be, it will be above center. If it is at the top, then you believe that you are 1.0 seconds (or more) ahead of the server. If the bar reaches the top or bottom, then your client will re-synchronize itself with the server (it will smash its clock).

Ideally, no bars should be visible whatsoever. That is, you have 0.0 seconds of latency, 100% of data from the server is getting to you, and your client believes that it is at the same point in time as the server. In practice, this will not happen.

The (L)atency bar will almost always be visible since it is not possible for data to get from the server to you instantaneously. The higher the latency, the longer it takes for data to get from the server to your computer, and so the older it is when it gets there. The older the data is, the more "predicting" your client has to do about the positions of other cars on the track. The more that it has to predict, the more likely that it will predict incorrectly, and the more the other cars will jump around when it realizes its error.

It is not uncommon for the (Q)uality bar to be completely empty (indicating little or no data loss), but it is also not uncommon for a few percent of the data to be lost or garbled during transmission, showing as a small (Q)uality bar. If the bar starts to grow steadily, then something bad has happened on the route through the Internet between you and the server (or the server has crashed). If the route doesn't clear up quickly, you will soon be disconnected. If it does clear up, there will probably be short period of mayhem as the route settles down, and old data that has been stuck in transit is flushed.

If the latency is varying a bit, it can be difficult for your client to determine what point in time the server is currently at, and a small (S)kew bar is likely to appear. If the (S)kew bar grows continuously until it hits the top or bottom, your client will smash its clock to re-synchronize itself to the server. If it does this, then either the connection between you and the server is very poor, or either your machine or the server machine is extremely overloaded, and your client can no longer stay in step with the server.

http://www.youtube.com/watch?v=Jji6iq0lwpU

iRacing vs Reality comparison - Watkins Glen CUP with Daytona Prototype

This is what happens when you turn off the SR system to a grid full of FW31's ... very messy.. from 20th to 5th place in one lap

http://www.youtube.com/watch?v=XIoRPkz_M-8

Quote from Swiss-Spirit :

Hands and steering wheel doesn't move, and the driver looks like a crash test dummy, he doesn't even move a little

Ah well if thats how you want to judge you sims, then i feel sorry for you, its only you missing out

Its Week 13.. things are a little different.. it will go back to normal series next week

http://www.youtube.com/watch?v=8-xzjwbS3bA

http://www.youtube.com/watch?v=COGleDFzL5c

Yes please sir!

Red Bull gives you wings. At least, it does if you're Vettel