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
Doesn't this only affect the main menu, not in game?
Trust me, many people on higher end hardware do it to try and get better reg/performance - maybe it'll help with your tab lag?
I have this problem. And in my case, i have a work around.
If you join a server and it lags, change the resolution to something lower. Then change it back to you native resolution. it compleatly remove the lag.
KONGKALH
It seems like that if Steam is installed on the ext4 system drive and playing the games from a secondary drive formatted as ntfs and/or mounted with fuseblk it will cause this frame drop. After formatting my game drive to ext4 and reinstalling, Counter Strike seems to be running fine.
This is caused because these partition types do not use the same standards for storing data and data transfer.
You can check what your drives are formatted by typing 'sudo blkid' in Terminal/xterm.
Example output
/dev/sda1: LABEL="Storage" UUID="538ae91d-d49b-40ba-92a2-64eac8651e16" TYPE="ext4"
/dev/sdb1: UUID="8a575537-3950-45cb-84cc-740d3adbe365" TYPE="ext4"
/dev/sdb5: UUID="4bc15ef7-610e-46f6-9f09-ec5334df9eae" TYPE="swap"
If the type is listed as 'fuseblk' or 'ntfs' you may need to use GParted to get it formatted to the correct file system.
Hope this helps.
Well actually, there are reports of this happening on i7 4790k and i7 5820k machines. I personally don't run an amazing processor, AMD 8320, but just figured I would give an FYI to anyone still experiencing this problem..