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
Do you connect using IP or client?
With locking AC to CPU 0 core only and csgo to cores 2-15 it seems working much better.
If i block AC from effective working by flooding core 0 with high priority stresstest at core 0 (so the AC has no CPU power for disposal) i dont see any difference in performance/input lag in csgo. So the primal activity of AC itself is not causing the input lag. I suspect the reason of input lag is that the AC steals/burdens system resources from csgo what i prevented it from doing now.
Now im gonna to test it at faceit servers.