Getting Started

Get a feel for the autoexec setup, binding config, and more

In this guide you'll find a variety of advice and tips to make your game run better, have more customizations, and have plenty of binds to change your game on the fly. Overall, if you spend some time investigating into this, your gameplay will improve!

I split the guide up into 5 different categories. CVARs drive right into the core of the game. Most of these variables won't outright improve your gameplay, but will allow you to tweak and customize it to fit your style. Binds are a collection of useful binds, that allow you to perform many actions with a single click of a button. Scripts are larger compilations of cvars, binds, etc, and are useful in many different situations. Configs offer a full set of cvars, binds, and such to create a useful environment for Competition, Server Admin, Demo Playback, and other settings. Other is left for everything else, that is uncategorized.

Suggested Config Setup:

Set vs Seta commands:
Seta stores the command and makes it permanent. Set isn't so permanent (if its out of the autoexec, anyway). Source

Help! I've changed a value of a cvar, but I want to change it back!
If you use the command in your console, without a value attached to it, it should give you an explanation (if available) as well as the default value.
IE: try typing in r_brightness into your console, by itself.

Tip: Try using the TAB key when using console commands. It'll automatically fill it out, or give you a list of elements you can look it.

Cvars

CVAR stands for "Configuration Variable". We determine what CVARs are useful to you!

Quick List


Detailed List

Alt-Tab Fix
Use the Alt-Enter Fix to allow Alt-Tab. Alt-Enter will put your game into Windowed mode, then you can Alt-Tab. But wait, can't Alt-Enter? Use this command to be able to.
seta com_useFastVidRestart "1"

Enable Console
Normally CTRL-ALT-~ will work, but if you enable it ~ will work normally.
seta com_allowconsole "1"

Expand your Field of View
I use a Field of View of 105 (default is 105), I find it is the best. Give it a chance, it does seem very weird at first, but has helped me immensely.
Note you should use a bind to switch between your new FOV and the default (90). This is because the Titan is glitched, and you need an FOV of 90 to use it properly.
seta g_fov "105"

Skip Intros
Skip the beginning intro. 'Nuff said.
seta g_skipintro "1"

Less Obtrusive Voting
Tired of the voting box showing up, even after voting? Get rid of it AND increase it's transparency!
seta gui_voteAlpha ".5"
seta g_voteKeepVote "0"


Advanced CVARs

Increase View Distance
Increases view distance and view distance details! These will impact performance, so you may need to tweak settings.
seta image_lodbias "-1"
seta r_visdistmult "1.2"

Use all VRAM
Set this variable to your VRAM. My VRAM is 256, set to yours. May be a good idea to just type com_videoram in console, to see what the detected setting is, before changing.
seta com_videoRam "256"

Dual Core CPU Tweak
As of the 1.2 Patch, you can make use of Dual Core (multi-threaded) CPU functions. 1 sets it to a Locked mode, whereas 2 is Unlocked. To fully make use of your CPU, set it to 2.
seta r_useThreadedRenderer "2"

FPS Smoothing
Advanced Users Only! While this tweak is noticable, it does require some testing to ensure it works properly.
First thing you need to do is unlock the FPS. This takes out the 30fps cap the game has by default. Note: even though you may render faster than 30fps, the game still runs physics & network at 30fps.
seta com_unlockfps "1"
Next, we need to set a timing method. Here's the description from the console:
method of timing interpolated/extrapolated frames: 0 = whenever they fit; 1 = on boundaries of framerate multiples of 30; 2 = like 1, but using total previous everything time to estimate, not just render time.

Let's be honest, that's just confusing. Here's a better (and longer) description.

I'll sum it up: "0" has the maximum FPS, but it's not that smooth. "1" smooths out the frames, but doesn't quite give you as much raw FPS. "2" should smoothen it out the most, but most people report added "jitters" to the game, and I've seen it first hand. I recommend the value of "1" to everyone, but be sure to test out "0" and "2" to see if they suit your computer & setup better.
seta com_unlock_timingMethod "1"
We're not done, yet. If you set your timing method to "1" or "2", you need to set a max FPS. Please note it must be a multiple of 30 e.g. 60, 90, 120. There is no reason to set it above 120, and you should pick the max FPS close to what your max FPS really is. I use 120, but only because I get high FPS due to low graphics settings (for competition).
seta com_unlock_maxFPS "120"

Network Client Prediction
From TweakGuides:
[This Cvar] determines the number of additional milliseconds by which the client (your machine) will try to predict and offset any ping lag. The default is 20ms, but if you're experiencing connection problems and lag and/or have a high ping, raising this value may improve things. Remember however that your ping is the round-trip time to a server (e.g. a 150 ping means 75ms taken for your data to get to a server, 75ms for it to get back). So your ping divided by 2 will give you the best prediction value, and usually only if your ping is higher than 150ms.
Now, I think this is a bit too high, personally. After some testing, I found "15" to be the best setting for me (even though my ping is 50-100 on most servers, even higher). This may be because I play competition smaller servers, and there is less lag in general. However, high ping players will probably want to set this ABOVE the default of "20". Test it out with the Lag O Meter.
seta net_clientPrediction "15"


Binds

Create & use custom binds to enhance your game and give a more dynamic experience.

Coming Soon

Scripts

Check out these pre-built scripts, and customize them to fit your needs.

Fireteam Script
From TweakGuides:
[This Cvar] determines the number of additional milliseconds by which the client (your machine) will try to predict and offset any ping lag. The default is 20ms, but if you're experiencing connection problems and lag and/or have a high ping, raising this value may improve things. Remember however that your ping is the round-trip time to a server (e.g. a 150 ping means 75ms taken for your data to get to a server, 75ms for it to get back). So your ping divided by 2 will give you the best prediction value, and usually only if your ping is higher than 150ms.
Now, I think this is a bit too high, personally. After some testing, I found "15" to be the best setting for me (even though my ping is 50-100 on most servers, even higher). This may be because I play competition smaller servers, and there is less lag in general. However, high ping players will probably want to set this ABOVE the default of "20". Test it out with the Lag O Meter.
Here's the script. I use the key ALT-F1. To change the varibles, take out the _STUFFHERE_, but keep the '' on it.
bind F1 "fireteam disband;fireteam create; fireteam name '_NAMEHERE_'; fireteam private; fireteam invite '_MEMBER1_'; fireteam invite '_MEMBER2_'; fireteam promote '_FIRETEAMLEADER_'; addchatline '^2Fireteam ^8Created'" "alt" "default"

Here's mine:
bind F1 "fireteam disband;fireteam create; fireteam name '^8Hell^bKatz'; fireteam private; fireteam invite 'hk|-Torn'; fireteam invite 'hk|-Slotz'; fireteam invite 'hk|-Seba'; fireteam invite 'hk|-.space.'; fireteam invite 'hk|-RotBot'; fireteam invite 'hk|r-s1n'; fireteam invite 'hk|-Mattc0m'; fireteam invite 'hk|r-masume'; fireteam invite 'hk|-Millon'; fireteam promote 'hk|-Mattc0m'; addchatline '^2Fireteam ^8Created'" "alt" "default"

Configs

Check out these fully-featured configs for competition, demo player, server admin, and more.

Coming Soon

Other

Everything else is collected & presented here.

SPECIAL THANKS TO THESE CONTRIBUTORS

Working on finishing it up... Thanks for your time!