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
"mat_queue_mode [-1,0,1,2] - This setting determines the threading mode the material system uses. A value of -1 uses the default for your system, a value of 0 uses synchronous single thread, 1 uses queued single threaded mode, and value of 2 uses multi-threaded mode. Many users report performance increases on multi-core systems when setting this variable to a value of 2."
http://www.reddit.com/r/GlobalOffensive/comments/1x697n/fps_fix_inside
Generally it should be set in the "autoexec.cfg" file or a file called by it.
It sets the Materials System Queue mode, which determines how queued textures and shaders are rendered. There are various settings to turn on and off the use of the materials queue for various things.
The default ("-1") usually detects properly and turns on multi-threaded on multi-core systems, but this isn't always the case. If it is not detecting properly, or you think it isn't, then you can turn it to "2".
In some games "-2" is available, which uses an alternate default detection algorithm. In other games it will be the same as "-1" or "0" depending on the game. I'm not sure how Counter Strike: Global Offensive handles this.
Please note that this variable can expose bugs in games, which generally consist of texture, shader or shadow glitches. If you notice such things you can either turn it back to "-1" or you can try turning off use of the threaded material queue system on specific functions with other variables. (e.g. r_queued_ropes, r_queued_decals, r_queued_postprocessing).
I'm not sure if it's the same as the -threads command line option, that may control something different, or a parent function that this uses.
Get my old fps back so can somebody help me? (Sry my english sucks)
didint work :/
When you say mat_queue_mode 2- you mean mat_queue_mode 2 rigth ? I'm asking this to make sure that having this " - " is the same thing of not having ?