Slap's Config Options

[SLAP]

hey guys I was just wondering if any of you have ever tried altering your config to better your performance in game (FpS). I have been working on configs since the beggining of cod2 and i think it helps my gaming ability incredibly. I figured i would post a link to my config if anyone wants to try it out, if you don't know how to put it in I can post a walkthrough for you, but it is def worth trying.

Don't worry its all legal in both CAL and TWL and alot of people are using this one now...cause it owns

try it tell me what you think, and if you have any questions ask me.

S L A P' S config

[SLAP]

well i noticed that a few of you downloaded it and hopefully i'll get some feed back. If anyone doesn't understand how to use the config, or if anyone wants me to customize it to fit their PC let me know.

Basically i just want to see what you guys think, and i'm beyond positive that it will improve your gaming if its used/customized.

don't be afraid to post

[Old Man Mike]

Hi SLAP,

Thanks for posting this. I was going to reply earlier but things were a bit busy around here. Anyway, I have a few questions:

1) You have binds for cl_packetdup 3 and 5. Also cl_maxpackets 30, 63 and 100. Do you often change these? If so, what is your decision process? I am most surprised that you don't have a cl_packetdup bind for 1 since the higher numbers slows your transmit time (but can help if there are packet losses or errors).

2) I see that you run only 800 x 600 for your display. Do you have to run this low to achieve your 125 fps setting? Have you tried a higher resolution with AA changed from 1 to 0? The polygonoffset bias and scale do seem to help for the lower resolutions but no so much (if at all) for the higher resolutions.

3) Why r_intensity "1"? It appears to be an unknown command when typed in console.

4) What are the r_picmip, bump and spec setting doing? It seems these settings were more important before the 1.2 Patch.

Those are the ones I noticed but there may be other questions after a more detailed review.

Old Man Mike

[SLAP]

Hi SLAP,

Thanks for posting this. I was going to reply earlier but things were a bit busy around here. Anyway, I have a few questions:

1) You have binds for cl_packetdup 3 and 5. Also cl_maxpackets 30, 63 and 100. Do you often change these? If so, what is your decision process? I am most surprised that you don't have a cl_packetdup bind for 1 since the higher numbers slows your transmit time (but can help if there are packet losses or errors).

2) I see that you run only 800 x 600 for your display. Do you have to run this low to achieve your 125 fps setting? Have you tried a higher resolution with AA changed from 1 to 0? The polygonoffset bias and scale do seem to help for the lower resolutions but no so much (if at all) for the higher resolutions.

3) Why r_intensity "1"? It appears to be an unknown command when typed in console.

4) What are the r_picmip, bump and spec setting doing? It seems these settings were more important before the 1.2 Patch.

Those are the ones I noticed but there may be other questions after a more detailed review.

Old Man Mike

Those are good questions man
1) My binds for packet dup are for when i use different guns in the game, I use packet dup 3 for mg/rifle and packet dup 5 for shotty. This helps regestration a little bit, plus if i feel like i'm getting a lot of packet loss I can bumb my dup up to 5 in a hurry for better reg.
Maxpackets is another command for regestration, 63 is ideal for if you get 125 FPS but if i feel i am not registering my shots I bump it up to 100...and if i want to show off a low ping in a chi server i bump it to 30

2) I do run my game in 800x600 purely for performance, it is about the only way for me to hit 125...plus i've gotten so used to it I kinda like it. On a side note the config will obviously work just as well for anyone if they choose to change it out of 800x600. The polygon commands boosts my fps a lot, and pretty much every other texture is set to the lowest setting to boost FPS, High FPS = faster running, highter jumping, faster shooting

3) r_intensity is a command from other games on the same engine...so it works with CoD2. It adjusts overall strength of RGB color intensity, of which the base value is the color White. This has the visual effect of something akin to adjusting brightness (but not quite). Increasing this value would make everything "brighter" at the cost of texture detail. Does not impact performance. Not available in any in-game menus.

4) You cought me, those picmip bump and spec commands are all old ones that I just never took out of my config, to be honest I forgot they were in there

any other questions please let me know, and let me know if you want me to tell you how to keep your configs from being changed depending on the servers you are in....the more servers change them the less consistant you will be

[Genocide Junkie]

Can you send me the command for faster and more precise hand eye coordination?

[SLAP]

Can you send me the command for faster and more precise hand eye coordination?

rofl

[Old Man Mike]

Can you send me the command for faster and more precise hand eye coordination?

/r_purgeold


Old Man Mike

[Capt. Andtennille]

Can you send me the command for faster and more precise hand eye coordination?

I would like that as well as the commands for;

Better in-game decision making.

Chosing the weapon I actually want rather than the one I get when I use the scroll button on my mouse.

Adding the "Abuse Seeking" rounds to all my weapons.

Voice-to-text so I can communicate with temmates who are not on vent without getting killed.

Command to stun my wife when she get's upset that I'm playing so much.

[blk96gt]

Command to stun my wife when she get's upset that I'm playing so much.

Just punch her in the throat, that'll take her down for a while.

[Old Man Mike]

Command to stun my wife when she get's upset that I'm playing so much.

Just punch her in the throat, that'll take her down for a while.

Blk talks big but I bet his ear is quite red. Red from his wife draging him around by it.

"yes dear", "right away dear", "whatever you want, dear" .........


Old Man Mike

[steel]

I'd like the cod2 settings for "make this work exactly like coduo" - LOL!

[{CuF}crazycanuck]

I'd like the cod2 settings for "make this work exactly like coduo" - LOL!

heres a set of fps tweaks we use...sorry Slap i hope i'm not hopping on your post here. i didn't download yours yet but will definitely check them out.

The only issue i have had is when i uncap my fps..i hace to cap them for some servers. i use basically the same settings for Cod2 but i posted the COD2 tweaks as well for you.

I have never used the PB tweaks...so i cannot speak for what they do.
********************************************************************************
*************************************************
Here are some tweaks to improve performance, courtesy of BC from FKmod.com :

****Make sure you back up the config file!****

In your uoconfig_mp.cfg (uo folder) make sure your hunkmegs is set to half of your total system memory.



seta cm_playerCurveClip "1"
seta com_hunkmegs "512" <-- set to half of your total RAM (max is 512)
seta com_introplayed "1"
seta com_maxfps "0" <-- Make sure that it is set to zero (pb doesn't like this setting ,i set to 150)


One of things that helps is set the fps to the refresh rate of your monitor. In your uoconfig_mp.cfg file:


seta r_diffuseSunSteps "3"
seta r_displayrefresh "85" <-- add this. ( oronly what your monitor supports)
seta r_dlightQuality "1"


Only set the displayrefresh to the refresh rate your monitor can support. lcd monitors do not need a higher refresh rate, leave at native setting


Also in your Call of Duty/pb folder, create a pbcl.cfg file and put the following:


pb_sleep 500
PB_SsLog 1
PB_SsSave 1
pb_LogToFile 1
pb_logmd5tool 1



Another thing to do:

Pull open the console and type in /rate. If this number is not 25000 and you have a cable/dsl (fast) connection you will get lag at points. Type in /rate 25000 to set it properly.



This is for those with broadband connections:

seta cl_maxpackets "100"
seta cl_packetdup "1"
seta snaps "40"
seta rate "25000"


This is suppose to improve network issues...
********************************************************************************
************************************************
********************************************************************************
************************************************

AND HERE ARE SOME COD2 TWEAKS...

The first step would be to fix your "config" file

first Do this:

Make a back up copy of your "config_mp.cfg" First!!

Click on
My Computer
Local Disk "C:\" for most people
Program Files
Activision
Call of Dutry 2
Main
Players
"Name" (Your player name)
config_mp.cfg (open in wordpad) (MAKE COPY AND SAVE NOW BEFOR YOU EDIT)

or

C:\Program Files\Activision\Call of Duty 2\main\players\ (Your player name)

OPEN WITH WORDPAD....EDIT/Change the following:

seta cg_drawFPS "1"
seta cg_drawLagometer "1" <---- (if you want to see if its server lag or PC lag)
seta cl_maxpackets "100"
seta com_hunkMegs "512" <----(or set to half your RAM (512 seems to be the top number regardless))
seta com_maxfps "125" <----(set to "0" for high end cards Not illegal but pb doesn't like it)
seta rate "25000"
seta snaps "30"
(Save and Close)

IN GAME PLAY SETTINGS

This will show your in game FPS:

When your on a map in game
Click ~ key <----(brings up console)
type; /cg_drawfps 1
Press enter key
Press ~ key

Game Video options
Set the 'DirectX' to 'DirectX 7'


Some Common Commands
(some you have already done in your config_mp.cfg file but it will explain in detail below)

Click ~ key <----(brings up console in game)
or you can Edit in config_mp.cfg its up to you!

/cg_drawFPS
[0,1,2,3] - Displays the frames per second (FPS) counter at the top right of the screen. In simple mode (1) shows the average and current (low and high) FPS. In Verbose mode (2), additionally shows vertex counts. In Time mode (3) shows the time taken to draw the current frame in milliseconds (ms).

/com_introplayed
[0,1] - If set to 1, skips the introductory Activision/Infinity Ward movies played at Call of Duty 2's launch.

/com_maxfps
[0 - 1000] - Determines the maximum frames per second (fps) possible. If set to 0, disables the FPS cap. Any value higher than 0 caps your FPS to that level. The main reason to use this command would be to smooth framerate fluctuation, as framerate spikes can cause jerky gameplay.

/com_hunkMegs
[80 - 512] - Determines the amount of memory (in MB) to allocate to the game to help smooth out in-game loading. You should not allocate any more than half your system RAM to this option (i.e. if you have 1GB of RAM, set this cvar to 512).





Demo Commands

cl_avidemo
[0,1] - If set to 1, begins recording frames for a demo movie. These frames are stored in .tga format in your \Program Files\Activision\Call of Duty 2 Demo\Main\screenshots folder. Note that enabling this option can severely slow down your system, and it can be disabled at any time by setting cl_avidemo to 0.

Record [demoname] - Starts recording an in-game demo with the filename you specify. The file is saved under your \Program Files\Activision\Call of Duty 2 Demo\Main\demos directory as a .spd file.

StopRecord - Stops recording the current demo.

Demo [demoname] - Plays back the pre-recorded demo specified. Note, to play back a demo you must be in the game menus - demos can't be played back while you're in-game.

timedemo [0,1] - If set to 1, enables timedemo mode. Once a pre-recorded demo is played, the timedemo results are shown in the extended console, and the results are saved as a .csv file in your \Program Files\Activision\Call of Duty 2 Demo\Main\demos directory.

[SLAP]

so, has anyone tried the config...if so any feedback?