PDA

View Full Version : TF2 Tweaks


]LoL[Harm
01-16-2008, 04:13 PM
This was originally posted bout OutZ over at the MyU forums. I use them, and maybe they'll help others in loading times and whatnots.


-----------------------------------------

I just wanted to share some TF2 tweaks that are essentially borrowed from CS:Source.

Mouse Tweaks:

First we need to take care of Windows and make sure it isn't applying any kind of acceleration to your mouse movements. Go here and get Accelfix, this link also provides information on what exactly it does:

http://razerblueprints.net/index.php.../topic,6898.0/ (http://razerblueprints.net/index.php/component/option,com_smf/Itemid,99/topic,6898.0/)

Now lets make sure TF2 isn't altering your mouse movements:

1) Right click on your TF2 shortcut, and click on properties.

2) In the 'Target' field you will see something like this (X is the drive you installed Steam on):
X:\Steam\Steam.exe -applaunch 440

3) Change it so it looks like this:
X:\Steam\Steam.exe -applaunch 440 -noforcemparams -noforcemspd -noforcemaccel

This will tell the game to use your desktop mouse settings, and not to apply any kind of acceleration to your aim. Then just set your sensitivity in-game to whatever suits your style and uncheck mouse filtering if it is checked.

The Autoexec.cfg. It's source's version of the UT.ini/User.ini. There are many variables in the source engine, and I don't attend to list them all here. What I'm providing here is what I use and recommend everyone uses. These variables do not dumb down the graphics, or effect rendering in any way, but rather will give you the best network performance.

1) Browse to your TF2 cfg directory. It should be something like this (X is the drive you installed Steam on):
X:\Steam\steamapps\your-name\team fortress 2\tf\cfg

2) Make a new text document, and inside copy and paste the following:

//cl_commands
cl_forcepreload "1" // This will preload all the game content at once, instead of loading it on an as-need basis which can cause stuttering or slow downs.

//misc_commands
fps_max 300 // This will prevent your FPS from being capped, 300 is max.

//optimal netcode_settings
cl_cmdrate "101"
cl_interp "0.01"
cl_lagcomp_errorcheck "0"
cl_lagcompensation "1"
cl_smooth "1"
cl_updaterate "101"
rate "25000"

3) Save the text file and name it: Autoexec

4) Change the Autoexec.txt extension to Autoexec.cfg

That's it, now every time you load the game it will automatically load those settings.

Grundy
01-16-2008, 04:57 PM
Hmm 300 fps? Im getting 22-25 ish at 1024x768 using the default recommended* settings. I'm gonna try dumming down the video settings...

Ok I upped resolution to 1280 and lowered video settings to Low. Game looks the same and I am getting 40 - 65 fps.

]LoL[Harm
01-17-2008, 05:25 AM
Thats just the max Grundy, most people don't operate that high, the setting just eliminates any cap that may have existed.

Post
01-17-2008, 07:27 AM
I wish they had config files run like they used to in classic (or maybe it was all the way back to qtf?). Each class ran its own config file at your spawn. For example, if you chose a demoman, it ran a demoman.cfg file, then if you chose a spy later, it ran a spy.cfg file and so on and so forth.

Morety
01-17-2008, 10:07 AM
40-65 fps is a good rate. You don't need more than that.

spyder913
01-17-2008, 03:17 PM
Post, I'm pretty sure you could at the very least do that with bindings.

Grundy
01-17-2008, 04:20 PM
I have seen class specific sub-cfg files tied to the autoexec.cfg but I havnt tried any as of yet. One trick people use is to play a wav file when they pick the class specific cfg so they can hear which one it is.

exec scout.cfg
exec soldier.cfg
exec pyro.cfg
exec demoman.cfg
exec heavy.cfg
exec engineer.cfg
exec medic.cfg
exec sniper.cfg
exec spy.cfg

This one uses the Arrow button to cycle thru each of the exec files.
http://www.fpsbanana.com/scripting/2422