Counter-Strike 2

Counter-Strike 2

View Stats:
Yuppi Jan 23, 2014 @ 6:26am
Launch options - multicore rendering
Hi, I've been crashing multiple times this week during a competitive and almost been banned because of that.

I think the reason why I'm crashing is because the "Multicore rendering" is on enabled and not disabled. But.. Just now I realized that everytime I close the game and then enters it again, the Multicore rendering is on Enabled again.

So my question is, is there any launch options-command for disabling this? So I don't have to do it every single time I launch CS:GO..

Thanks // Yuppi
< >
Showing 1-15 of 27 comments
Hiphastis Jan 23, 2014 @ 6:29am 
there is no command. You turn it off in the options menu and hit apply, and no it will not have reset itself when you reboot the game. Also if you're on a laptop due stop playing GO on it, as a laptops crashing games is a sure fire way to know your hardware is too weak for the job. (1200$ laptop with dedicated GPU at the minimum)
Last edited by Hiphastis; Jan 23, 2014 @ 6:29am
c00kie ツ Jan 23, 2014 @ 6:29am 
You can disable this in your video.txt in the cfg directory of CS:GO.

settings_queque_mode "0" or something like that
Yuppi Jan 23, 2014 @ 6:30am 
Originally posted by Here Kitty Katie:
there is no command. You turn it off in the options menu and hit apply, and no it will not have reset itself. Also if you're on a laptop due stop playing GO on it, as a laptops crashing games is a sure fire way to know your hardware is too weak for the job. (1200$ laptop with dedicated GPU at the minimum)

Well I don't have a laptop, I have a decent gamingcomputer but it's getting slow and old, like every computer is.

And yes, it does actually reset everytime I quit CS:GO, I can promise you that.
Hiphastis Jan 23, 2014 @ 6:31am 
Originally posted by c00kie:
You can disable this in your video.txt in the cfg directory of CS:GO.

settings_queque_mode "0" or something like that

that sounds like a strange command, that relates nothing at all to multi-core rendering.
Yuppi Jan 23, 2014 @ 6:31am 
Originally posted by c00kie:
You can disable this in your video.txt in the cfg directory of CS:GO.

settings_queque_mode "0" or something like that
What exactly does setting that to 0 do?
Hiphastis Jan 23, 2014 @ 6:31am 
Originally posted by Yuppi:
Originally posted by Here Kitty Katie:
there is no command. You turn it off in the options menu and hit apply, and no it will not have reset itself. Also if you're on a laptop due stop playing GO on it, as a laptops crashing games is a sure fire way to know your hardware is too weak for the job. (1200$ laptop with dedicated GPU at the minimum)

Well I don't have a laptop, I have a decent gamingcomputer but it's getting slow and old, like every computer is.

And yes, it does actually reset everytime I quit CS:GO, I can promise you that.

I also own the game on my other rig to which i have it enabled (thanks in part to my card having multiple rendering cores). Disabling that setting is only used for really really old hardware like GTX 9800
Hiphastis Jan 23, 2014 @ 6:32am 
Originally posted by Yuppi:
Originally posted by c00kie:
You can disable this in your video.txt in the cfg directory of CS:GO.

settings_queque_mode "0" or something like that
What exactly does setting that to 0 do?

it tells the program not to run that partciluar command when the game boots and you set it to 0 to do that.
c00kie ツ Jan 23, 2014 @ 6:32am 
"setting.mat_queue_mode" "0" // Multicore Rendering Disabled
Last edited by c00kie ツ; Jan 23, 2014 @ 6:33am
Hiphastis Jan 23, 2014 @ 6:33am 
Originally posted by c00kie:
"setting.mat_queue_mode" "2" // Multicore Rendering

beware with that advice just like in Source if you use that command you risk it sticking and not changing back when you change hardware. just letting the OP know you only turn that command off if your GPU is of a certin age as it wont provide much of a fix (crashing happens 99% of the time due to weak hardware)
Last edited by Hiphastis; Jan 23, 2014 @ 6:35am
c00kie ツ Jan 23, 2014 @ 6:34am 
Dude look this command up and change it to 0
Hiphastis Jan 23, 2014 @ 6:35am 
Originally posted by c00kie:
Dude look this command up and change it to 0

he will change it to zero, just make sure you tell him about the potential break that said fix you provided causes.
c00kie ツ Jan 23, 2014 @ 6:38am 
There is no risk dude.
Hiphastis Jan 23, 2014 @ 6:40am 
Originally posted by c00kie:
There is no risk dude.

the risk is, the command remains perm (its happened in source and GO). Also if his rig only uses a single core for rendering, he may cause even more lag if the card he has indeed has at least 2 rendering cores (just about all cards after 2007 have this).

Multi-core rendering is typically disabled when your card is incapable of such a thing. having it off last i checked put more effort on the CPU
Last edited by Hiphastis; Jan 23, 2014 @ 6:41am
c00kie ツ Jan 23, 2014 @ 6:40am 
But if the game crashes with multicore rendering its stupid to activate it.

just set down the quality to low.

my game also crashed with MR enabled and i turned it off, set the quality to low and now it works. I got only dual core but it works.
Last edited by c00kie ツ; Jan 23, 2014 @ 6:42am
Hiphastis Jan 23, 2014 @ 6:41am 
Originally posted by c00kie:
But if the game crashes with multicore rendering its stupid to activate it.

just set down the quality

Well yeah, just turn down all the settings really until a stable fps is attained, if that cannot be done upgrade the hardware. i get no crashes with a GTX 670.
< >
Showing 1-15 of 27 comments
Per page: 1530 50

Date Posted: Jan 23, 2014 @ 6:26am
Posts: 27