This CS:GO config comes from years of accumulating information from various sources and maintaining it up to date with every game update introducing new features and deprecating others.
This config has been revorked for training on maps that wasn't ported to cs2, maps for training are located in csgo_config\cfg\trainingmaps.cfg
This project includes the wonderful Orel's Text Mod and awesome BananaGaming's Color Mod available here: https://gamebanana.com/gamefiles/3711, and here: https://maximhere.me/modifications/, that will greatly simplify radio messages displayed in the chat.
Some part of the README are based on a great reddit post by /u/birkir: https://www.reddit.com/r/GlobalOffensive/comments/8ax858/updated_csgo_tips_configs_and_more/.
You can find a list of all the available CS:GO Cvars here: https://developer.valvesoftware.com/wiki/List_of_CS:GO_Cvars, it contains a description and the possible value of every one of them.
Navigate to where you want to store the config files, for example $HOME/Documents, then:
git clone https://github.com/rawreflect/csgo_config.git
cd csgo_configEdit the copy-cfg-files-linux.sh script to verify that the CSGO_INSTALL_PATH variable is identical to your CS:GO install path and change it if that's not the case, then:
chmod u+x copy-cfg-files-linux.sh
./copy-cfg-files-linux.shVerify that the files were correctly copied by running:
ls -l /path/to/your/csgo/cfgDownload an archive of this repository by clicking the "Clone or download" green button on the topish right of this page and then clicking on "Download ZIP".
Copy the downloaded csgo_config-main.zip file to the folder where you want to store the config files, for example %USERPROFILE%\Documents and unzip it.
Edit the copy-cfg-files-windows.cmd script to verify that the csgo_install_path variable is identical to your CS:GO install path and change it if that's not the case.
Right click on the copy-cfg-files-windows.cmd file and click on "Execute as Administrator".
Verify that the files were correctly copied by navigating to your csgo cfg folder and checking if the .cfg files of this project are present.
You don't need to add +exec autoexec.cfg to your CS:GO launch options but you need to add -language textmod or -language colormod to enable the Orel's or BananaGaming's Text Mod.
From now on you shouldn't modify CS:GO settings[1] by using the in-game menu. If you do so your modifications will be overwritten by the settings stored in the .cfg files the next time you open CS:GO. If you want to modify a particular setting you will need to directly edit the corresponding .cfg file.
[1] The only exception is video settings that are not modified by the autoexec.cfg file.
For optimal use, you shouldn't delete the folder that contains the git repository that's in your Documents folder in order to edit the files it contains later and just re-execute the copy-cfg-files script again.
For example if you want to enable Demo view mode you just need the execute the demos.cfg file by opening the console (by pressing = or whatever you have set toggleconsole to in your binds), typing exec demos or demoview shortcut and pressing ENTER. Same thing if you want to enable Other configs, use exec "config" respectively.
The config itself is pretty personal so you will have to edit the files in order to tailor it to your preferences.
If your internet bandwidth is less than 6 Mbps (megabits per second) you should change the rate in the autoexec.cfg file to the appropriate value:
| Bandwith | rate |
|---|---|
| 0.5 Mbps | 65536 |
| 1 Mbps | 131072 |
| 1.5 Mbps | 196608 (default) |
| 2 Mbps | 262144 |
| 4 Mbps | 524288 |
| 6+ Mbps | 786432 |
-tickrate 128 -novid -nojoy -exec autoexec +cpu_frequency_monitoring 2 -language colormod
tickrate 128how many times per second the server calculates stuff. tickrate 128 - highest possible tickrate in CSnovidto skip the video intro.nojoyis required for me since the Panorama update on Linux because I have an Xbox One controller plugged-in at all time and CS:GO crash at launch in this situation. See this github issue to learn more.exec autoexecused to automatically execute the configcpu_frequency_monitoring 2to see if CPU thermal throttling is an issuelanguage colormodto enable the BananaGaming's Text Mod.
VibranceGUI, in-game vibrance level: 150- VibranceGUI will automatically enable AMD Saturation or Nvidia Digital Vibrance when a specific configured game is full-screened. It makes the in-game colors "pop" more while the desktop can stay at it's standard value. I chose 150 because it's a good compromise between the dull CS:GO default and the over the top maximal saturation.
Resolution: 1024x768 Stretched- It's down to personal preference and computer specs.
Display Mode: Fullscreen- For the lowest input lag, chose
Fullscreenbecause it give the game direct access to the graphics output without the OS interfering and adding display lag.WindowedandFullscreen windowedwill make alt-tabbing faster but because the video frames has to pass through the OS before being displayed it will add some display lag.
- For the lowest input lag, chose
Here's a great (pretty old but still relevant) 3kliksphilip video on all the graphics options below if you want to learn more: https://www.youtube.com/watch?v=ns9srRoDop8.
Here's another (more recent and also relevant) 3kliksphilip video on Effect Detail and Shader Detail effect on molotov's smoke particles: https://www.youtube.com/watch?v=s5-aqgwBhM4.
Global Shadow Quality: High- Shadow quality affects the render distance of players shadows so you need the highest one to be able to see them in all situations. Because shadows can giveaway players position you want to be able to see them in all circumstances. On the other hand
Very lowdisable a lot of the pre-baked models shadows which helps with visibility and players shadow can still be visible from really close but that's not enough for me.
- Shadow quality affects the render distance of players shadows so you need the highest one to be able to see them in all situations. Because shadows can giveaway players position you want to be able to see them in all circumstances. On the other hand
Model/Texture Detail: High- The resolution of the textures, lower the value if you don't care about it or have little amount of VRAM. There's pretty much no downside to using higher detailed textures in this game so go for it if you can.
Effect Detail: Low- As explained in 3kliksphilip's video on molotov visibility, if you want less fire smoke at a distance, set
Effect DetailtoHighandShader Detailto at leastHigh. On the other hand if you want less fire smoke close-up, set one of the two to something other than theHighorVery Highvalue.
- As explained in 3kliksphilip's video on molotov visibility, if you want less fire smoke at a distance, set
Shader Detail: Low- Affect reflection on surfaces, like your gun skin or water, rain and other parameters. If you want your gun skins to look good you need to set it to at least
Highbut if you care more about gameplay you should set it toLowas explained in the first 3kliksphilip video.
- Affect reflection on surfaces, like your gun skin or water, rain and other parameters. If you want your gun skins to look good you need to set it to at least
Multicore Rendering: Enabled- Allow CS:GO to use multiple CPU cores.
Multisampling Anti-Aliasing Mode: Disabled- Which version of MSAA or CSAA to use, higher value will look better but have a higher impact on performance. Don't use in conjunction with FXAA.
FXAA Anti-Aliasing: Enabled- An other type of AA, a lot less taxing in terms of performance but very bad in term of quality because it's just a post-processing effect. Don't use in conjunction with MSAA or CSAA.
Texture Filtering Mode: Bilinear- Enhance the image quality of textures when viewed at an angle. Performance impact really minimal. As said in the 3kliksphilip video you will want to set it to
Bilinearif you care more about visibility than prettyness.
- Enhance the image quality of textures when viewed at an angle. Performance impact really minimal. As said in the 3kliksphilip video you will want to set it to
Wait for Vertical Sync: Disabled- VSync, you absolutely don't want that in CS:GO.
Motion Blur: Disabled- Same as VSync, you absolutely don't want that in CS:GO.
HUD Edge Positions: All the way up to the edges of the screen- Down to personal preference but the smart choice would be to bring the edge of the HUD closer to the center of the screen so that your eyes will have less travel to do in order to look at it.
sensitivity: 1.1- I tried a huge amount of sens and I settled on 1.1, because for me it turned out to be the best, with it I can easily turn around, and in general I feel comfortable when playing, your value may differ and the sensitivity value is selected solely by you and under you.
DPI: 800- I use one of the most common DPI, Before I used to use 400 DPI, but I had problems using the mouse inside windows and other programs / applications / games, your value may differ and the DPI value is selected solely by you and under you.
Polling Rate: 500Hz- The amount of time per second that your OS will poll your mouse. If you have a wired mouse you want to set this to it's highest value possible. If you have a wireless mouse you also need to think about battery life and maybe set it to 1000Hz or 250Hz if you don't feel any difference.
Contributions are welcome if you see any area of improvement possible to the scripts or if there's new CS:GO config variables to tweak!