
Another thread about
Counter Strike: Source BETA and its
FPS and Configuration files (.cfg)s
by Brenton 'Mz' Smith.
Where to begin?
- Where are my configuration files?
- What are my configuration files?
- What does all this stuff mean! (*Confused*)
- Everything explained... as much as I can.
- Finally some extra things that might help you out!
Just before I continue I have posted each of the larger section into SPOILERS to reduce the viewing size of this post!
Where are my configuration files?
All configuration files can be located for example:
C:\programfiles\steam\steamapps\**Username**\Counter Strike Source BETA\cstrike_beta\cfg
What are configuration files?
SPOILER: Click to viewAutoexec.cfg // This file will load automatically upon each fresh game start.
Config.cfg // This file contains specific information in regards to personal preferences.
All of your in-game configurations are based upon these two files in particular. However the definitions I have provided are very straight forward they can be slightly different and cross-over occasionally (without any harm of course).
On to the question at hand, what are configuration files? In a nutshell these two main configuration files do relatively similar jobs but I will try to expand upon this a little further than the brief descriptions I provided earlier.
Autoexec.cfg: The most important of the two in regards to in-game performance the correct setup of this file can be make or break for some low end users who experience unneccessary FPS Lag.
- Generally speaking (15 to 30 FPS) is considered bareable. (30 to 60 FPS) Decent and (100+ FPS) an advantage.
Please note: Regardless of your opinion towards How many frames the human eye can see. There are many factors that come into play which range from lighting, to retinal fusion points and image artifacts which are created at lower frame rates. These factors impact everyone differently and really depend on how the images are being displayed.
(I will speak about how to boost your frames up a little shortly)
Config.cfg: Plain and simple this file contains your keyboard binds and mouse binds, some more broad sighted graphical options which are available via the (Advanced Video) menu. This file only needs to contain these default variables and should generally be left alone unless you are changing your controls or making some short key binds.
What does all this stuff mean?
This following spoiler will contain only the commands in which really effect your frame rate the most. A short description of what kind of changes it will make to your game will follow each variable.
SPOILER: Click to view
Mat_ options
mat_picmip "0" // Default: "0" - Changes Texture quality Level
mat_antialias "0" // Default: "0" - Changes Anti-aliasing Level
mat_aaquality "0" // Default "0" - Anti-aliasing quality 4/2 = 8xCSAA, 8/2 = 16xCSAA
mat_forceaniso "2" // Default "2" - Antiscopic Filtering
mat_reducefillrate "1" // Default "1" - Shader Detail Level
mat_hdr_level "0" // Default "0" - High Dynamic Range Lighting
mat_bumpmap "0" // Default "0" - Bumpmap Texturing
mat_specular "0" // Default "1" - Specular Lighting
R_ options
r_lod "1" // Default "1" - Models level of detail
r_rootlod "1" // Default "1" - Root model level of detail
r_decals "100"
// Default "200" - Amount of decals (Bulletholes, sprays, etc) that can be on the world at one time
r_drawdetailprops "0" // Default "0" - 'Detailed' props, such as grass
r_drawflecks "1" // Default "1" - Impact debris
r_shadows "1" // Default "0" - Player Shadows
r_shadowmaxrendered "5"
// Default "4" - The amount of how many fully rendered player shadows will be drawn - anything else is rendered as a blur oval shadow
r_dynamic "0" // Default "0" - Dynamic lighting
r_3dsky "0" // Default "0" - Render the 3D skybox projection
r_waterdrawreflection "0" // Default "0" - Water reflection
r_waterforceexpensive "0" // Default "0" - Detailed water
r_waterforcereflectentities "0" // Default "0" - Allow water object reflection
r_propsmaxdist "0" // Default "0" - Maximum visible distance of props
r_worldlights "0" // Default "0" - Lights that reflect off your weapon
r_renderoverlayfragment "0" // Default "0" - Overlaid textures that make up decal like effects
r_ropetranslucent "0" // Default "1" - Enable/Disable ropes
Rope_ options
rope_smooth "0" // Default "1" - Antialiasing effect on ropes
rope_wind_dist "0" // Default "1" - Don't simulate wind on ropes past X distance
rope_collide "0" // Default "1" - Collide rope with the world
rope_subdiv "0" // Default "1" - Rope subdivision amount
Client_ options
cl_phys_props_max "0" // Default "0" - Maximum clientside physic props
cl_ragdoll_physics_enable "0" // Default "0" Enable/disable ragdoll physics
cl_ragdoll_collide "0" // Default "0" - Ragdoll collisions
cl_ragdoll_fade_time "0" // Default "0" -Time until ragdolls disappear
These settings are default for Counter Strike: Source and BETA although are altered when more advanced video options are changed.
These settings may be of some help to low end users experiencing FPS loss but not all are needed. They merely effect the look and quality of the in-game graphics and are a personal preference. Pretty? or Fast?
All of the above variables are most probably the biggest changes that your game will ever make in terms of performance. As every machine is different and finding that perfect setup is crucial I would recommend playing with each of these tweaking your configurations to suit your PC and/or Laptop.
Extra food for thought.
Everyone that has tried out the new BETA has most probably played with a few other people online. The main two things being said by players are "
Why am I losing frames? and Why is it taking so long to load?"
Your computer is NOT setup correctly OR its time for an UPGRADE
"But I can play Counter Strike: Source normally fine!"
There are a few things that you can do to help. As the game is still in BETA and after all it is a new engine that it is running on.
Try using some lunch options. These will help you to force Counter Strike: Source BETA into using some extra resources ect. Have a look at the list below and give some a try. After all its all about learning, why not give each one a go and see what it does for you?
You can add these lines to your Counter Strike: Source BETA launch by right clicking it in your steam game list and selecting "Launch options"
SPOILER: Click to view
Ram Help!
-heapsize 131072 // If you have 256Mb RAM
-heapsize 262144 // If you have 512Mb RAM
-heapsize 393216 // If you have 768Mb RAM
-heapsize 524288 // If you have 1Gb RAM
Misc.
-console // Starts the game with the developer console enabled
-dxlevel <level>* // Forces a specific DirectX version when launching the engine.
Note: You must multiply your DirectX level by 10 eg. (DirectX 8 = -dxlevel 80)
-32bit // Forces the engine to start in 32-bit mode. (For those with 64-bit systems)
-w <width> // Forces the engine to start with resolution set to <width>.
-h <height> // Forces the engine to start with resolution set to <height>.
-refresh <rate> // Force a specific refresh rate.
-heapsize <kilobytes>* // Specifies the heapsize (in kilobytes) the game will use.
-nosync // Forces the specific game to not use VSync.
-low // Forces the specific game to launch in a LOW process priority.
-high // Forces the specific game to launch in a HIGH process priority.
-threads // Forces the game to use a specified amount of threads for a multicore CPU (2 for Dual, 4 for Quad).
Apologies for the sloppy post. I wish I had more time this week to write one up in more detail and make a bit more sense. Everything in this post will effect your PC's performance in one way or another and there is no real correct combination. Each computer is different and must be setup differently.
As there are not that many different things to try I suggest that giving each of these a look in a create a server and seeing what they do for you might be a good idea.
Thanks for everyone thats had a read and I hope that its helped you a little.
Mz.Edited once, 26/5/10 - 10:06am.
Posted on Wednesday, 26th May 2010