The only variable that we cant control that can effect how good we race is our network, the current red/green bar does'nt tell us a whole lot imo.

I propose to have these cars look like they are equipped to race in a virtual envoirment with a nice three bar led display on the dash- YES real race cars dont have them...but real race cars are not network traffic dependant.

Ping>Packet loss>Lag(PPL)

Heres a rough sketch:

Do you want the car to speak with you too?

However, -1
This is network debug info and has no place on the dashboard.

Quote from AndroidXP :

Do you want the car to speak with you too?

However, -1
This is network debug info and has no place on the dashboard.

I feel it does as we are in a virtual envoirment it is the achilles heel of how well you race

i agree with CSU1 HE IS THE BEST!

Is it really? I never pay attention to it and yet have to experience any problems. Though, it probably depends on the general quality of your connection on how important these bars are. But it's never important enough to warrant a physical place in the cockpit. That's just an immersion killer.

Quote from AndroidXP :

Is it really? I never pay attention to it and yet have to experience any problems. Though, it probably depends on the general quality of your connection on how important these bars are. But it's never important enough to warrant a physical place in the cockpit. That's just an immersion killer.

Thats what i'm talking about. If you for example are hammering along through traffic and dust, full grid...you know that your hardware is up to the task the only remaining variable is the general quality of your connection.

The first bar - Ping.
would relate to the direct connection of you the client to the master server.

second bar - Packet loss.
would indicate if your machine/network struggling to deal with too many packet transactions; beit other applications or accounts using network bandwidth.

last bar - Laggggg
self explanitory.

Quote from AndroidXP :

Do you want the car to speak with you too?

Quote from androidXP :

But it's never important enough to warrant a physical place in the cockpit. That's just an immersion killer.

.... i agree i suppose. this should be easy enough to do myself using that insim thingy/i think

I think that the 'lag bars' we have could be improved as well...they don't really tell you that much.

When I used to play CounterStrike, the net_graph command would give you a display of latency, choke, packet loss etc, and was the first thing you looked at if you were suffering connection issues.

Quote from Bean0 :

I think that the 'lag bars' we have could be improved as well...they don't really tell you that much.

my point exactleu.

There's nothing you can do to improve your network connection while driving. So what good would it bring to be able to check it in such details in real time? If your connection gets too bad LFS drops you and that's it. Am I missing something?

You would instantly know if another peice of software or your OS is using bandwidth hence choking your system.
You would also know not to take the sharp corner in record time with 3 other racers during this period of time.

+1 as long as it's not sticking out like a sore thumb.