Why....this is really starting to annoy me.

[divVerent]

Then why don't I get these lags?

Maybe the ISPs the server are hosted are bad (in case of RBI servers, the university network in Frankfurt, Germany)? But for me at home (T-Online) that works fine.

Actually, I took the freedom to ping Demitar's IP (he often gets lag issues on my server) from my university server... I got:

Code: Select all

--- ****.broadway.se ping statistics ---                                                                                                                          331 packets transmitted, 274 received, 17% packet loss, time 329975ms
rtt min/avg/max/mdev = 57.837/78.775/100.143/7.457 ms

No, I don't expect DP or any other FPS engine to be able to cope with that much loss.

And I got the same amount of loss from my home connection to him.

Anyone who gets lag issues on my server, please try ping 141.2.16.3 (or on Windows, ping -t 141.2.16.3) for a while (maybe five minutes) and then press ^C to get the packet loss stats. I am sure you won't get 0% of packet loss.

[Beowulf]

Code: Select all

--- 141.2.16.3 ping statistics ---
768 packets transmitted, 753 received, 1% packet loss, time 767252ms
rtt min/avg/max/mdev = 135.512/140.208/207.571/6.137 ms


Not bad, but sometimes I do get lag spikes where I just have to quit. (it's fun to stop and look around while everything is frozen).
It's probably my wireless lan or my flatmates downloading teh pr0n.

[Dokujisan]

sure, your flatmates

[divVerent]

Code: Select all

--- 141.2.16.3 ping statistics ---
768 packets transmitted, 753 received, 1% packet loss, time 767252ms
rtt min/avg/max/mdev = 135.512/140.208/207.571/6.137 ms


Not bad, but sometimes I do get lag spikes where I just have to quit. (it's fun to stop and look around while everything is frozen).
It's probably my wireless lan or my flatmates downloading teh pr0n.

1% loss? That's more like 1.95%... and even 1% loss is quite much and should not happen.

[Beowulf]

It's interesting that ping truncates the percentage like that.
I think that for my amount of packet loss, the only culprit is my wireless connection.

I am sure you won't get 0% of packet loss.

even 1% loss is quite much and should not happen.

[Urmel]

Sometimes I ask myself why Nexuiz is sucking for me although (or especially while!!!) ping is 0 and pl is 0% shown on the pingometer and while other players dont seem to hace any problems at all. But this happens only @work where at least a slightly busy exchange server is doing his stuff at the same time. Is it possible htat there is something else that can not be measured in pings or PL% ??

btw: min 14ms, max 87ms (huh), avrg. 15ms, PL: none (775 packets sent/received) > at home

[SavageX]

Is it possible htat there is something else that can not be measured in pings or PL% ??

Sure. Jitter - meaning that on average the ping may be okay but that the actual ping time per packet may fluctuate. If this happens "older" packets can be received *after* their successors are received, thus meaning they can be received in the wrong order. Delayed packets are basically useless, although technically they are not "lost" in the strict meaning.

[Urmel]

Okay, I dont understand a word. Currently I played on pussydelight an it was thumpy like hell.

ping -t ran and it resulted as follows:


Pakete: Gesendet = 891, Empfangen = 891, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 18ms, Maximum = 33ms, Mittelwert = 19ms

[divVerent]

This is some jitter, but not much - the numbers also indicate absolutely NO packet loss (1% is bad, but you got an exact 0%).

Can you try again with cl_movement 0 on the same server?

[ZWERG]

Is it possible htat there is something else that can not be measured in pings or PL% ??

Sure. Jitter - meaning that on average the ping may be okay but that the actual ping time per packet may fluctuate. If this happens "older" packets can be received *after* their successors are received, thus meaning they can be received in the wrong order. Delayed packets are basically useless, although technically they are not "lost" in the strict meaning.

Now this explains a lot! I have about the same problem: Stuttering up to a degree where it is unplayable sometimes and yet Nexuiz shows <30 ping and no packetloss.
I always thought: Damn, the packetloss value in the scoreboard must be wrong.

I know it's because my connection is shared with others, some are even watching video streams that eat up 80% of the bandwidth.
It's clear that there must be out of order packets, either with me when I'm playing or with the ones who are watching video streams.
Now the question is, why are out of order packets not counted as lost packets?
They are useless, that's for sure, the players' positions are already updated when they're received.