Whisper wrote:
On a 33 tickrate CS SRCDS the clients never receive more than 33.9 updates per second (yeah its not exact, but its close enough) therefore a sv_maxupdaterate of 60 is a complete waste, and if it is not, then I have not seen a explanation as to the rationale why!
What if the process of the tick and the sendout procedure aren't synchronized? Let's look at this: Time 1: New tick Time 2: Time 3: Update sent out Time 4: New tick Time 5: Time 6: Update sent out Both updates and ticks are at the same rate, but there is a delay between a new tick and the information getting to the client. With a bigger updaterate it would be like this: Time 1: New tick / sending update Time 2: Time 3: sending update Time 4: New tick Time 5: sending update Time 6: So clients will get their new information faster, more accurate of what really happens on the server. That was always my thought on that. With kind regards, ]FUSION[ Gray Death _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
