Luk4ward Posted January 7, 2007 Share Posted January 7, 2007 (edited) Hi, some1 gave me the link to such article because of my lag spikes...But now it is very useful for players who are kicking by punkbuster with such errors: md5tool ignoring queries/cvars pb init failure com_maxfps: While this setting will not usually* improve your connection it does help stop the confusion between connection lag and graphics related lag when, for example, jumping from 85 FPS to 23 FPS. Set this by monitoring your FPS while playing using cg_drawFPS "1" and set com_maxfps to your average steady FPS rate It is also the case that as your FPS increases so does the data size of each packet sent to the server. In extreme cases with a very high FPS you could saturate your upstream connection. See snaps for another extreme case where reducing com_maxfps may help. : High values of com_maxfps can cause "connection interrupted". Exactly what value causes this depends on your ping and net settings, but it usually happens between 200-400 fps. This is usually caused by internal data structures getting filled up, rather than actually saturating your connection. In addition, the game will send at most 1 packet per frame, so having cl_maxpackets == com_maxfps may have some advantage. If they are not equal, various rounding may cause your effective maxpackets to be lower than you would expect snaps: The snaps setting is used to calculate how many gameworld updates you receive from the server. Usable range is 10 to 'server sv_fps setting' and defaults to 20. Version 1.17 of Quake3 forces snaps client side to a maximum of 25 or in some cases a maximum of 30. However the network code works in such a way that snaps should always be set to match or be above the server's sv_fps or a divisor of it. Leave snaps at your default until you encounter a server that needs a higher/lower setting : snaps should always be 20 (or maybe 10 on dialup), since the server will never send more than one snap per server frame, and varios things in ET break if sv_fps is not 20. ETpro will force your server to run at sv_fps 20. Setting snaps higher than sv_fps won't give you more snaps, but it can confuse the rate limiting code, so don't do that. My recommediation: snaps 20 cg_predictItems: Toggles whether the server or the client decides if an item has been picked up. I dislike this feature and set it to 0 so that the server determines if I have picked up an item and not my client. With this set to 1 sometimes you may think you have picked up an item when you have not. cg_nopredict: Best to leave this setting alone, defaults to 0 which enables client side prediction so that your client predicts gameworld updates such as player movement when information is lost or capped. Setting this to 1 disables all client side prediction. pb_sleep: This setting is related to Punkbuster, setting the period of time that PunkBuster "sleeps" between processing, defaults to 60. Players with slow (modem) to medium (ISDN) connections should set this between 300 and 500 to reduce 'lag spikes' . rate: it controls packets so that your downstream connection bandwidth does not get saturated. Setting controls maximum bytes per second. Servers limit maximum rate so there really is no point in setting it higher than the server you are playing on allows : rate should be 25000, unless you are on a low bandwidth connection. While you can technically set rate higher, 25000 is near the maximum that the engine will actually be able to send. cl_timenudge: This is similar to pushlatency in HalfLife, defaults to 0 which is our suggested setting for online play. In Quake3 it is normally used for offline bot practice by using a positive value that is the same as average ping. However, a positive value can also be used to stabilize displayed frames with gameworld updates(snaps) and negative values are reported to adjust client side prediction. We strongly suggest you leave cl_timenudge at 0 for online play. However If you do wish to alter cl_timenudge to adjust client side prediction then try a negative value that is 25% to 50% of your average ping. Example if you are currently pinging 100 to the server then experiment with a setting between -25 to -50 as your cl_timenudge value. Note that if you are using a negative value for cl_timenudge the top graph in cg_lagometer may be mostly yellow. A positive value may help if you have problems with gameworld updates (snaps) not being rendered in time. Try a small positive cl_timenudge value of 5,10,15 or 20 never higher. See cg_lagometer for an explanation of how to determine if gameworld updates are not being rendered in time. *note: Some admins force to have set this to 0, because server allows dialup connections or because that they want to do that :P, as suggest punkbuster... cl_packetdup: This setting determines if duplicate commands are sent, range is 1 to 5 and is 1 as default. if a packet gets lost then a 'backup' command may still be received. Set to 1 as default which is recommended if you have packet loss. If you have an excellent connection with very little or no packetloss at all then this could be set to 0 and cl_maxpackets possibly raised. However, as with all settings experiment to see which is best suited for your connection - See cg_lagometer for a guide on how to determine if you need to adjust this setting. cl_maxpackets: The cl_maxpackets setting restricts the number of packets being sent to the server by your client and can be used to help connection bandwidth related problems for those with low upload bandwidth. The default setting for cl_maxpackets is 30, usable range is 15 to 100 on the Internet, maximum 125 under point release 1.32 or above. id software force a higher value when playing over a LAN. * As your FPS increases so does the data size of each packet sent to the server. In extreme cases with a very high FPS you could saturate your upstream connection. In all cases try to set cl_maxpackets to equal your average framerate or your com_maxfps setting or a divisor of it without saturating your upstream bandwidth. Use the FPS figure displayed using cg_drawFPS "1" as a guideline for actual FPS. For Example if you are currently at com_maxfps "76" then try a value of 38 or 76 for cl_maxpackets. If you have set your FPS above 100 then use a divisor of your FPS, for example if you are currently capped at 125 FPS then try 31/32 or 62/63 as a cl_maxpackets setting. See the note about packetloss in the cl_packetdup entry. When playing on a Punkbuster enabled server you may need to reduce cl_maxpackets and/or adjust pb_sleep to reduce lag spikes. cg_lagometer: Set this to 1 to monitor your connection - The first line is related to your graphics card updating displayed frames in time with received gameworld updates from the server. It will be blue if frames are being rendered in time with the world updates. If it has a lot of yellow then gameworld updates are not being displayed and are being dropped. In this case reduce your snaps or tweak your visual settings to raise your average framerate so it is always above your snaps setting. Another option is to increase cl_timenudge by a very small value, note that if you are using a negative value for cl_timenudge the first line of the graph may be mostly yellow. See cl_timenudge section for more information. The second line is similar to the Quake2 netgraph in that green means packets are being received okay, yellow that capping is causing your client to reject packets and red that the packet was lost. In the case of yellow increase your rate or try lowering your snaps. If you have a lot of red then change ISP or server. If you have to play on the server or use the ISP then make sure that your cl_packetdup is set to 1 and try adjusting snaps and cl_maxpackets to compensate for the lost packets. ReyalIp: The lagometer is described here http://wolfwiki.anime.net/index.php/Lagometer How to put these commands to your config: seta name of command "value" example seta snaps "30" Suggested settings are in the table that follows. They are however guidelines, adjust them as needed by monitoring your connection using cg_lagometer and alter settings based on its information. See the description of how to use and interpret the information that cg_lagometer shows in the above table. It is very important that you read the cg_lagometer, snaps and cl_packetdup notes before you use these settings. If you do not see an exact connection speed setting then use the closest. Example, perhaps you connect at 50000 or 52000 on modem, use the 48000 setting from the table. * Note: The snaps settings shown in the table are the suggested maximum for your connection type. Default is 20 and is the suggested setting. See the snaps description in the table above for a link to a snaps setting cycle script and information regarding some servers deviating from id software's standard server setting for sv_fps. ** Note: The cl_maxpackets settings shown in the table are the suggested maximum for your connection type, other settings may be optimal for your connection. See the cl_maxpackets description in the table above for more information on setting this cvar. LAN ** seta cl_maxpackets "125" seta cl_packetdup "0" * seta snaps "40" seta rate "25000" ADSL / Cable / Wireless ** seta cl_maxpackets "100" seta cl_packetdup "1" * seta snaps "40" seta rate "25000" ISDN Bonded ** seta cl_maxpackets "60" seta cl_packetdup "1" * seta snaps "40" seta rate "(See Table Below)" 128000 BPS: seta rate "14000" 112000 BPS: seta rate "12250" ISDN Single ** seta cl_maxpackets "60" seta cl_packetdup "1" * seta snaps "40" seta rate "(See Table Below)" 64000 BPS: seta rate "7000" 56000 BPS: seta rate "6200" 56K Modem seta cl_maxpackets "30" seta cl_packetdup "1" * seta snaps "20" seta rate "(See Table Below)" 50000 BPS: seta rate "5500" 48000 BPS: seta rate "5200" 46000 BPS: seta rate "5000" 44000 BPS: seta rate "4800" 42000 BPS: seta rate "4500" 40000 BPS: seta rate "4300" 38000 BPS: seta rate "4100" 36000 BPS: seta rate "4000" V34 Modem seta cl_maxpackets "25" seta cl_packetdup "1" * seta snaps "20" seta rate "(See Table Below)" 33600 BPS: seta rate "3500" 31200 BPS: seta rate "3300" 28000 BPS: seta rate "3000" 28.8 Modem seta cl_maxpackets "25" seta cl_packetdup "1" * seta snaps "10" seta rate "(See Table Below)" 28000 BPS: seta rate "3000" 26400 BPS: seta rate "2800" Minimum Bandwidth Settings - Testing purposes or temporary settings while lag settles. seta cl_maxpackets "15" seta cl_packetdup "0" seta snaps "10" seta rate "(See Table Below)" 64000 BPS: seta rate "6000" 56000 BPS: seta rate "5000" 50000 BPS: seta rate "4600" 48000 BPS: seta rate "4400" 46000 BPS: seta rate "4000" 44000 BPS: seta rate "3800" 42000 BPS: seta rate "3600" 40000 BPS: seta rate "3500" 38000 BPS: seta rate "3200" 36000 BPS: seta rate "3000" 34000 BPS: seta rate "3000" 33600 BPS: seta rate "3000" 31200 BPS: seta rate "2800" 28000 BPS: seta rate "2600" 26400 BPS: seta rate "2400" As for examples of settings, yes they are pointed to q3 so if u r lazy u can copy past, but i suggest to try individual values for all commands if u know what is your bandwitch (check your speed: link) and how many max fps u can get. In ET u can also see other internet settings by typing: /players source : http://ucguides.savagehelp.com/ConnectionFAQ/Quake3.htm I doubt any of these settings will fix the PB errors for many people. The only exception would be if you are on a very low bandwidth connection (ISDN/Dialup) you need to make sure you don't saturate your connection. Note also that the quoted article is for q3, so isn't entirely applicable to ET. In practice, most servers limit netsettings to values that will be unplayable on dialup and single channel ISDN. ************other notes************** Some problems may cause other applications so i recommend to turn them off. You should get some good antivirus (like nod32) and firewall (like look n stop), because of their smallest size and power. They do not cause any lags. You have to remember to allow communication between you and punkbuster, so if u got some problems with some crappy firewall u should do this: 1) Open the port in firewall, for example: 16000 and call it PB. 2) Open notepad and write: pb_netport 160003) Save it for example: pbcl.cfg4)Put it in the wolfet/pb/ ************other notes************** You can also update your punkbuster: 1) By pbweb.exe from wolfet/pb 2) Or by: http://www.evenbalance.com/index.php?page=pbsetup.php regards, hope i helped Edited January 7, 2007 by Luk4ward Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.