[daveyboye]

Originally Posted by Bacardi Nope, it isn't. It's default rate value for players now, when they play game first time, if they don't know how use console or change rate settings. "rate" = "50000" ( def. "30000" ) archive - Max bytes/sec the host can receive data Before OB update, default rate value was 10000, really LOW and cause choke and high pings etc. etc. when server run tickrate more than 33. Those settings have stayed from HL2 game. Sometimes even 30,000 is not enough in TF2 game, there happen lot of action when all players attack in same time. ---------------------- Spoiler Spoiler Spoiler I have thinking, those who host big server (30 players or more) and can't keep that updaterate staying to 66, so its start drop close to 30 and back 60 etc. etc. up and down. Why not try cap update rate to 20 or 30 ? What I have tested (with bots), it work very well. And will take less bandwidth. Spoiler sv_maxrate 0; sv_minrate 30000 sv_maxupdaterate 20; sv_minupdaterate 20 sv_maxcmdrate 66; sv_mincmdrate 30 sv_client_cmdrate_difference 100 net_splitpacket_maxrate 30000

That's good to know. I've heard so many conflicting reports on this. I've heard it's capped at 30,000 and that it will display what you have set in console, but it defaults to 30,000 anyway. Is there a way we can prove this wrong. Will net_graph 3 show any difference in packets if we set at 30k and then maybe 60k for example?