I use net_channels repeatedly whilst changing my netcode settings. Your client netcode settings if they are to be optimised need to consider: -client side FPS -server side FPS (roughly) -server tickrate -network bandwidth -network switching rate (unlikely to be exceeded)
Most of the above are simply cap's which you dont want to exceed. If you change your netcode settings and see excessive choke, you have gone over your cap for one of the above. The server can only process packets as fast as it's framerate. Similarly, the server only requires packets at the tickrate to achieve optimality - some consider "a few spare" to be reasonable also, although I do not share this view as cl_cmdbackup exists. You cannot generate packets faster than your client framerate - setting your cmdrate higher than your framerate can cause excessive choke. Your connection will have a limit to the number of packets it can send and recieve per second, and this will of course vary with packet size also. In general you should not exceed this, and on a boadband connection you will not exceed it on a 66 tickrate server (assuming your ISP are not complete morons). Now the easiest way to optimise your netcode is with trickle settings and essentially educated emperical testing. You should have an idea of the range of your settings: - No need to exceed 66 packets per second so cmdrate and updaterate <= 66. - No need to exceed framerate so cmdrate and updaterate <= average client FPS I would recommend setting: cl_cmdrate 66 cl_updaterate 66 set rate correctly as is documented many other places - maximum connection capability in Bytes per second. Check net_channels, you should see 66 packets per second on the inbound channel unless you are not on a true 66 tick (I have seen some scum running falsely advertised tickrates, a GSP no less) or unless your client is severely overloaded for bandwidth or processing. You will probably not see 66 packets per second on the outbound channel. What you will see is choke registering on the outbound channel - on any channel that has choke, lower your update and cmdrates until that choke is minimised. Not all clients can achieve 0.0 choke in all scenarios. On 7/24/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > -- > [ Picked text/plain from multipart/alternative ] > with new hlds update what should serverside and client side rates be ? > and with 66 tick i should see more than 33 on in and out on net_graph? > -- > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
