Online Gaming Issue.

[ManBearPig]

Why is it saying this in console (since ive downloaded that smartsniff thing)


NET_GetLong: Ignoring duplicated split packet 1 of 2 ( 1248 bytes ) from 72.232.197.29:27015
NET_GetLong: Ignoring duplicated split packet 2 of 2 ( 554 bytes ) from 72.232.197.29:27015
NET_GetLong: Ignoring duplicated split packet 1 of 2 ( 1248 bytes ) from 72.232.197.29:27015
NET_GetLong: Ignoring duplicated split packet 2 of 2 ( 52 bytes ) from 72.232.197.29:27015
NET_GetLong: Ignoring duplicated split packet 1 of 2 ( 1248 bytes ) from 72.232.197.29:27015
NET_GetLong: Ignoring duplicated split packet 2 of 2 ( 89 bytes ) from 72.232.197.29:27015
NET_GetLong: Ignoring duplicated split packet 1 of 2 ( 1248 bytes ) from 72.232.197.29:27015
NET_GetLong: Ignoring duplicated split packet 2 of 2 ( 436 bytes ) from 72.232.197.29:27015
NET_GetLong: Ignoring duplicated split packet 1 of 2 ( 1248 bytes ) from 72.232.197.29:27015

 

[Rabid Ewoks]

Rabid is with me on this one. Please set those to the defaults by typing:

cl_updaterate 20
cl_cmdrate 30

and then, please, confirm they are at default, by typing the command again, without the numbers, in the console.

Then play for the usual amount of you time you do for the game to begin stuttering.

Interesting how your PC wants the server to send more frames per second than the server wants to.... And your setting is five times the default rate.

I know with CS:S there is a setting called rate . It also has to do with how much you send. Also do you have any of the settings below? Try changing them to the values I posted.

cl_lagcomp_errorcheck "1"
cl_lagcompensation "1"
cl_smooth "1"

 

[NixJedi]

Fusion,

Do you think signal loss though would be something that affects packet segmentation and size?
I would have thought it would have affected packet transmission more by causing retransmits. The test Rabid recommended showed a pretty small retransmit rate.

(Still something we can see in a network trace!)

BTW: What is the normal dB loss? About -8 to -12?

For the RX (Recieve) around -5 to +5 is perfect. around or beyond -10 or +10 is horrible and would possibly knock a mdm offline. As for the TX (Transmission) -25 to +25 is within porper guidelines, where as -/+30 and beyond to past +/-55 is same thing: horrible and possibly would knock a modem offline.