Internet spiegazione schermata

[emifisa]

Oggi per la prima volta sono entrato in un server e non capisco cosa sono quelle 3 linee in alto a destra cosa indicano??

[Lalethor]

vado a memoria dato che non ho attualmente installato il sim

una dovrebbe essere il ping, le altre.... non me le ricordo pi

[emifisa]

Nooo non ho avuto tempo di cercare e poi con tutte queste pagine valla a trovare XD

[Lalethor]

Nooo non ho avuto tempo di cercare e poi con tutte queste pagine valla a trovare XD

che poi a dirti la verit

[Ginetto]

La spiegazione dettagliata c'è nel readme del gioco, riporto qui la porzione che riguarda le barre rosse

MULTIPLAYER - QUALITY METERS

------------------------------------------------------------------------------

NOTE: Turning the meters on might decrease your framerate and in some cases even

crash GPL!

The Internet can be a harrowing medium through which to race. Game play is

directly affected by the latency, reliability, and consistency of the connection

between you and the game server, so it's important that the program give you a

good sense of these factors. GPL 1.2.0.1 now has graphical displays that allow

you to monitor the status of your communications with the server when you are a

GPL client. These meters can only be displayed while in the car. They can be

toggled on/off by pressing Alt-M while in the car. They can be distracting

while driving, so they are turned off by default. You can request that they be

turned on by default by adding the following two lines to core.ini

[ Communications ]

show_meters = 1

The bar graphs are as follows...

(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. Note that Alt-L shows average latency, not instantaneous latency.

(Q) Quality from 100% (the bar is empty) to 0% (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 GPL 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.5 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.5 seconds (or more)

ahead of the server. If the bar reaches the top or bottom, then your

client will resynchronize itself with the server (it will smash its

clock).

Ideally, no red 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 resynchronize 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.

Edited October 7, 2009 by Ginetto

[emifisa]

Ma perchè usiamo l'inglese quando abbiamo la lingua più bella del mondo l'italiano XDXD

Comunque grazie mille

Edited October 8, 2009 by emifisa

[Ginetto]

Ma perch

[emifisa]

Ok grazie mille ho capito in poche parole servono a mostrati come vanno gli scambi di dati tra la tua conessione e il server e gli altri