destroy3r

what version of the cats would give me the best/most stable FPS with a 9700 pro

i really shouldnt have trouble getting good fps with this card :/

zerodamage

Give Omega's 3.9's a go. I get 100 fps steady on my 9500 pro and this is with 16x AF and 4x AA.

destroy3r

i cant seem to get stable FPS with the latest catalyst drivers... the fps goes high... but drops decently low.. this is bad cuz i need to spray well with ak/colt and i play semi-professionally

3.4s - trying now.. .they seem to help the FPS


Does anyone know if there is a fix for visual corruption with AGP fastwrite enabled?

Mazuko

Shouldn't be a problem with the drivers...I can hit 45 consistent FPS w/ a voodoo 3 1500 16MB PCI card.

Update your chipset drivers, and check out your rate settings (See the tables below).


If that doesn't work try these settings:

Rate
The command everyone should be able to tweak. The rate command sets the rate at which you transmit and receive data to the games server.

First thing I've found is you get the correct rate after alot of tweaking. Using odd values rather than the increments of 500 and 1000 to work best when finding your idea rate setting. You can fiddle with it by bringing down the console (` key) and typing "rate" in a range of values until you're happy. A good way to find if the you're using rate correct, is to have net_graph on. There is a few guildelines you can use to rate your connection, but it really depends on you're overall setup. Here is a fully detailed table showing recommended settings, don't be afraid to tweak it to suit yourself though.

LAN/T1/T3 cl_updaterate "40"
cl_cmdrate "40"
rate "10000"

ADSL / Cable / Wireless cl_updaterate "40"
cl_cmdrate "40"
rate "10000"

ISDN Bonded cl_updaterate "40"
cl_cmdrate "40"
rate "10000"

ISDN Single (Stac/Microsoft compression) cl_updaterate "40"
cl_cmdrate "40"
rate "(See Table Below)"
64000 BPS : rate "8000"
56000 BPS : rate "7000"

ISDN Single cl_updaterate "40"
cl_cmdrate "40"
rate "(See Table Below)"
64000 BPS : rate "6200"
56000 BPS : rate "5400"

56K Modem (Stac/Microsoft compression) cl_updaterate "30"
cl_cmdrate "30"
rate "(See Table Below)"
48000 BPS : rate "5800"
46000 BPS : rate "5500"
44000 BPS : rate "5200"
42000 BPS : rate "5000"
40000 BPS : rate "4800"

56K Modem (Hardware compression) cl_updaterate "20"
cl_cmdrate "30"
rate "(See Table Below)"
48000 BPS : rate "4600"
46000 BPS : rate "4400"
44000 BPS : rate "4200"
42000 BPS : rate "4000"
40000 BPS : rate "3800"

V34 Modem
(Stac/Microsoft compression) cl_updaterate "30"
cl_cmdrate "30"
rate "(See Table Below)"
33600 BPS : rate "4000"
31200 BPS : rate "3800"
28000 BPS : rate "3200"
26400 BPS : rate "3000"

V34 Modem
(Hardware compression) cl_updaterate "20"
cl_cmdrate "30"


To find your ideal rate setting first use the lowest rate value from the table related to your connection. Then go onto a server. Look at your ping. Now increase by +100 the value and watch your ping (wait 2 minutes between each rate change to allow time for connection to stablise at that new rate setting). Increase until you see your ping getting higher. Once it does that lower back down to the setting before and that setting should be the idea value for you.

Pushlatency
If you ever played CS on a LAN you'll know how good it feels to play in zero lag. Pushlatency helps bring back those feelings online.

Watch your ping and check for your average ping. Then use a value that is the same as your average ping or a value that is 50% of it. Remember it's pushlatency -<number> If you forget the minus sign latency will be added! This is only useful if you want to play offline, and want to add lag. When online use a negative value to help your connection appear smoother.


Tweakable commands

cl_cmdrate
Controls the amount of packets that are being sent to the server allowing you to tweak those bandwidth problems the rate above gives you a good idea of cl_cmdrate to use.

cl_updaterate
Appears to be the opposite of the cmdrate and depicts what game updates you receive.

cl_lc
To use this setting the server and modification must support lag compensation. When set to 1 the server will take into account your ping when deciding if you hit a player or not. If you have a very low ping or wish the older style of play then set this to 0.

cl_lc 1 (default)
Good Points: On a server that allows the function to work lpbs or hpbs with a decent connection can experience a more 6.1 version of aiming.
Bad: Only works on servers that allow it and may not be beneficial to people with a bad connection.
Note: Servers by default allow this function to work (sv_unlag 1).

cl_lw
This setting determines how weapons fire is controlled, for example with regard to sounds and animation. When set to 0 the client will perform as it used to prior to 1.1.0.0, the server returns/confirms weapon related fire information.

If you set this to 1 the client weapon sound and animation will happen as soon as you press fire. It should be noted that when set to 1 the animations and marks displayed are determined client side, as a result they may not be an accurate representation of where you are actually hitting.

You may find it useful to bind different settings of cl_lw and cl_lc for different weapons. It is very important to make sure that if you use a setting of 0 for cl_lw that cl_lc is also set to 0.

cl_lw 1 (default)
Good Points: Allows you to know when your weapons have fired due to the firing being controlled server side and not client side. Will again result in that beta 6.1 feel.
Bad: Only useful for people with a good connection. You may also find it is not a true representation of were you're aiming.

Recommended
HPB - Ping (999-150): cl_cl 1 & cl_lw 1 (default settings)
LPB - Ping (Below 150ish): cl_cl 0 & cl_wl 1

cl_showfps 1
Type this in the console to show your FPS (frames per second) in the top left hand corner.

max_shells 0
Default is 120, but if set to 0 will stop shells flying out from your gun. Saves a few FPS.

max_smokepuffs 0
Default is 120, but if set to 0 will stop the small smoke effects when you fire at any hard surfaces. Again will save you some FPS.

fps_max x
fps_lan, modem, have been removed and it looks like fps_max is the only command. Default is fps_max 72.

fastsprites 0
Better smoke effects.
0 = high quality (looks like smoke), 1 = (default), 2 = very low quality

Some of these settings may or may not work in CS 1.6, they all did in 1.5 and that was the last time I tested these. These were gathered from various sources as well as my own head. - Mazuko

__________________
E-bay feedback: http://feedback.ebay.com/ws/eBayISAP...me=STRK:ME:UFS