Increase FPS

[Revolver Ocelot]

This is a short guide I know, but it's worth it.

1.) First copy this line of text and paste in in a .txt document:

(Don't copy here)

cl_threaded_bone_setup 1
cl_threaded_client_leaf_system 1

r_threaded_client_shadow_manager 1
r_threaded_particles 1
r_threaded_renderables 1
r_queued_ropes 1

studio_queue_mode 1

gmod_mcore_test 1

// mat_queue_mode 2                // Dies

(Don't copy here)

 

2.) Then name that .txt: boost_on

 

3.) Then find the garrysmod directory, then place it in: GarrysMod/garrysmod/cfg

 

3.) You're done! All you have to do when you are in Garry's Mod type:

 

exec boost_on.cfg

 

or

 

Paste the code into the autoexec.cfg file in the GarrysMod/garrysmod/cfg (This is so you don't have to punch in the code everytime you start Garry's Mod.)

 

And watch as your FPS increases! (most of the time.) 

 

*Forgets to add what it actually does.*

What it does:

This basically increases the amount of cores the game runs on, like roast said (thank you for putting the answer down in the comments and reminding me.) The game default runs on one core, but with using this, it runs on multiple. Me personally I have had no problems at all using this method, but everybody is different. And it's not fully compatible and will most likely never be. So I advise you only to use this at your own hand.

[Revolver Ocelot]

2 minutes ago, VPN said:

I think you can just paste that into the "autoexec.cfg" file in the garrysmod/cfg folder

Thank you for the reminder, now I remember it, adding it now .

[CAESAR]

You havent even said what it does besides increasing FPS. What does it tweak?

[roast]

This could break things in game and crash your game. Garry's Mod is a single core game and doing this will make it run on more cores which it does not fully support (yet).

[Toast]

11 minutes ago, roast said:

This could break things in game and crash your game. Garry's Mod is a single core game and doing this will make it run on more cores which it does not fully support (yet).

Never*

[Lollipopxxxxx]

20 hours ago, Revolver Ocelot said:

This is a short guide I know, but it's worth it.

1.) First copy this line of text and paste in in a .txt document:

(Don't copy here)

cl_threaded_bone_setup 1
cl_threaded_client_leaf_system 1

r_threaded_client_shadow_manager 1
r_threaded_particles 1
r_threaded_renderables 1
r_queued_ropes 1

studio_queue_mode 1

gmod_mcore_test 1

// mat_queue_mode 2                // Dies

(Don't copy here)

 

2.) Then name that .txt: boost_on

 

3.) Then find the garrysmod directory, then place it in: GarrysMod/garrysmod/cfg

 

3.) You're done! All you have to do when you are in Garry's Mod type:

 

exec boost_on.cfg

 

or

 

Paste the code into the autoexec.cfg file in the GarrysMod/garrysmod/cfg (This is so you don't have to punch in the code everytime you start Garry's Mod.)

 

And watch as your FPS increases! (most of the time.) 

 

*Forgets to add what it actually does.*

What it does:

This basically increases the amount of cores the game runs on, like roast said (thank you for putting the answer down in the comments and reminding me.) The game default runs on one core, but with using this, it runs on multiple. Me personally I have had no problems at all using this method, but everybody is different. And it's not fully compatible and will most likely never be. So I advise you only to use this at your own hand.

this messed up my game my screen kept freezing but i could still type or walk

[roast]

On 01/04/2017 at 7:59 PM, Toast said:

Never*

[Revolver Ocelot]

On 4/2/2017 at 9:58 AM, james_emery said:

this messed up my game my screen kept freezing but i could still type or walk

I'm sorry to hear that ;(. If you fixed the issue, that's pretty good, but if the issue is still persisting and you want to get rid of this:

 

Fixing Method 1 (Manual): Don't type in exec boost_on when launching Garry's Mod

 

Fixing Method 2 (Automatic): In autoexec.cfg in the GarrysMod/garrysmod/cfg, delete everything in the text document pertaining this:

 

cl_threaded_bone_setup 1
cl_threaded_client_leaf_system 1

r_threaded_client_shadow_manager 1
r_threaded_particles 1
r_threaded_renderables 1
r_queued_ropes 1

studio_queue_mode 1

gmod_mcore_test 1

// mat_queue_mode 2                // Dies

 

(If this is all that's in autoexec.cfg, just delete everything in autoexec, obviously .)