Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Second - calibrate your PC by entering training game with bots. (To know how much player entities your PC can handle) When map will load enter cl_show fps 1 in console. Then kick all bots, then start adding them 1 by 1 until point where you will be satisfied with in-game fps. This way you will know how much players in one game session your PC can handle.
For example for me it's = 5 (my pc specs: core i3 2100, geforce gt-440 1gb, 8gb ddr3). I have 120fps on low graphics settings with high 3d models & textures turned on - on Mirage map without bots and 60 fps with 5 bots.
This is because something in CS2 player/bots entity system works wrong, cause fps starts to drop when you start increase players count on map and starts to raise when you decrease players/bots count. And by saying wrong I don't mean that it drops for about 10 or 15 fps...no...it drops about 100, 60 or 50 fps on various computer configurations)
It's not a normal behaviour for the game. It's the thing that Valve must fix, cause now it works very wrong.
Later on, it ran just fine.