How to unlock, increase and configure FPS

> >

Created 4 years ago

How to unlock, increase and configure FPS

FPS Knowledge Base - Everything you need to know about FPS
FPS is an abbreviation for Frames Per Seconds.
Playing with low framerates will significantly decrease the pleasure of gaming.
There are even special FPS values which will give you an advantage in movement so let's get deeper.

Unlock FPS:

By default CoD has only 60 FPS, even though the cvar com_maxfps is set to 85.
That's because of the vertical screen synchronisation which will adjust your framerate to your display refresh rate which is 60 Hz in most cases.
So first step is disable vsynch to get control over your FPS.

Start Call of Duty, go to options, enter performance settings and turn off vertical screen synchronisation (synch every frame).
After that open your console and write:
/cg_drawfps 1
/com_maxfps 0

The cvar cg_drawfps will enable the FPS counter.
The cvar com_maxfps sets a maximum limit for FPS (0 = no limit).
So this will show your current maximum possible FPS value in top-right corner while playing.

Increase FPS:

If your FPS are lower than 60 you probably have a flickering screen which is a big disadvantage while playing. Your maximum possible FPS value depends on the performance of your processor (CPU) and graphic chip (GPU).

You can only get a little FPS improvement with config tweaking so if your FPS are really low and you want to archive a higher rate, there is no way around buying better hardware or new computer.
If you plan to upgrade the hardware you need to have both a good CPU and GPU, upgrading just one of them while the other is still bad won't bring you a big improvement and isn't very efficient.

If you just need a little FPS boost you can improve your FPS rate by decreasing graphic quality and resolution in options. The lower the resolution and level of details and the more additional graphic effects are disabled, the less complex it is for your hardware to display the game which results in a higher possible FPS rate.

In addition to the graphic options you can improve your FPS a little bit with these cvars:
/r_fastsky 1
/r_drawSun 0

Close other programs:
You can improve your FPS also by closing processes running in background or other open programs.
This will help especially on single/dual core CPU's.

FPS change on view angle:
A real trick is looking into sky or on ground especially while jumping.
That way you save a lot resources and get much better FPS than looking straight into the field.

Configure FPS:

Next step is setting the correct com_maxfps value for your system.
The only valid values are those which are equal to (1000/x) where x is an integer.
If you set an invalid value you will get the next higher value.
Here is a list of possible FPS values so you understand it better.

Valid FPS Values:
1000/1 = 1000
1000/2 = 500
1000/3 = ~333
1000/4 = 250
1000/5 = 200
1000/6 = ~166
1000/7 = ~142
1000/8 = 125
1000/9 = ~111
1000/10 = 100
1000/11 = ~90
1000/12 = ~83
1000/13 = ~76
1000/14 = ~71
1000/15 = ~66
1000/16 = ~62
1000/17 = ~58
1000/18 = ~55
and so on...

Special FPS Values:

Everytime a frame is rendered by CoD your position is calculated, so if you're using a higher FPS value your positions gets calculated more times per second.
Some special FPS values result in rounding errors in CoD's calculations of the players position.
These FPS values have influence on the width and height of jumps, intensity of fall damage and how long you move silent.

While 76, 111, 125, 250 and 333 will give you advantages,
500 and 1000 will give you almost only disadvantages with a few exceptions.
All the others values have no real benefit and shouldn't be used.

FPS Effect on Jumping Height:

By default you jump 39 units high, but these FPS values have a boosting effect on the height.

76 FPS: 39.5 - 40 Units
111 FPS: 40 Units
125 FPS: 40.5 - 41 Units
250 FPS: 41.5 - 42 Units
333 FPS: 46 Units
500 FPS: Standing Up: 35 Units | In Movement: Up to 39 Units
1000 FPS: Standing Up: 35 Units | In Movement: Up to 39 Units

FPS Effect on Fall Damage:

This listings shows how much less or more percent damage you take compared to default fall damage.

76 FPS: -7% Damage
111 FPS: -7% Damage
125 FPS: -16% Damage
250 FPS: -20% Damage
333 FPS: -53% Damage
500 FPS: +89% Damage
1000 FPS: >+89% Damage

FPS Effect on Silent Walk:

This listing shows how long your footsteps are silent while walking compared to default.

76 FPS: 6% longer
111 FPS: - 21% longer
125 FPS: - 21% longer
250 FPS: - 37% longer
333 FPS: - 28% longer
500 FPS: Noiseless
1000 FPS: Noiseless

On some surfaces like the wooden bridges on harbor you are even noiseless with 333 FPS.
Also if you are holding heavy weapons like bar you can move completly silent with 333 FPS.

Setting the right amount of FPS for your System:

Now that you know everything about FPS you need to decide what value you want to go with.
Of course you can only choose between the values you reach consistently.
Setting com_maxfps 333 for example is no advantage for you if you effectivly just reach 200.

Personal FPS Ranking:
1. 333 FPS
2. 125 FPS
3. 250 FPS
4. 111 FPS
5. 76 FPS

If you don't even reach 76 FPS steady use 76 anyways, it's still better than any other value.

FPS related Cvars:

There are a few cvars which are related to FPS and should be set fitting your FPS value.
First off, write these cvars into console:
/rate 25000
/snaps 30

These cvars are about how much data the server will sent to you.
When CoD was released there were a lot of very low speed internet connections out there, that's why the default value is so low.
The values shouldn't be a problem for any basic internet connection nowadays.

The cvar cl_maxpackets defines the maximum of packets which will be sent to server per second.
The higher you set this, the smoother your game will feel as your actions (run, shoot, jump etc.) will be updated more frequently.
It's directly related to the com_maxfps cvar, so the actual number of packets you can send to a server is either one every frame, or one every two frames, or one every three frames and so on. So if you are running at 125 FPS, your possible cl_maxpackets values are:

125/2 = 63
125/3 = 42
125/4 = 32

125/1 = 125 is no valid value cause the maximum you can set is 100.
So if you are using cl_maxpackets 100 at 125 FPS, you are NOT sending 100 packets per second, you will send one packet every 2 frames, which is 62.5 packets per second.

So the recommended cl_maxpackets values depending on com_maxfps are:
IF:com_maxfps 333 THEN: cl_maxpackets 100

IF:com_maxfps 250 THEN: cl_maxpackets 100

IF:com_maxfps 125 THEN: cl_maxpackets 63

IF:com_maxfps 111 THEN: cl_maxpackets 56

IF:com_maxfps 76 THEN: cl_maxpackets 76

You may notice CoD showing a higher Ping if you increase your cl_maxpackets value, this can be ignored it's just a misscalculation.

Useful FPS binds:

Here I will show you some binds I personally use to have quick access on FPS related settings.

This will switch the value of com_maxfps between 76, 125 and 333 everytime you click F5.
/bind F5 "toggle com_maxfps 76 125 333"

This will either enable or disable the FPS counter everytime you click F6.
/bind F6 "toggle cg_drawfps 1 0"

These will set FPS to one specific value
/bind J "com_maxfps 76"
/bind K "com_maxfps 125"
/bind L "com_maxfps 333"

FPS depend on map:
Another point to mention is the bigger a map is and the more elements it has in it, the more power is needed by GPU and CPU to display it, which results in different maximum possible FPS values depending on map.
For example it could be that you have steady 125 FPS on mp_harbor but on mp_brecourt you only reach 90.
In this case you would need to switch your FPS to 76 and that's where a bind will become handy.

Get any amount of FPS you wish for, no matter what system you have:

There is the possibility to turn of rendering in CoD, that means your screen won't refresh as long it's disabled.
But while rendering is disabled you can set FPS to whatver value you want and get the benefit of this value.
This method is intended for use on low FPS systems for single jumps which require higher FPS values.

E.g. If you are playing with 125 FPS but you want to do a 333 FPS jump, write these commands into console:
/seta noRender "com_maxfps 333; cg_norender 1"
/seta doRender "com_maxfps 125; cg_norender 0"
/bind N "vstr noRender"
/bind M "vstr doRender"

If you stand infront of a jump and you know what movement is to do, but your FPS are too bad, get in position, press [N] to set 333 FPS and disable rendering and perform the jump.
When you are done press [M] to get your default settings back and check if you were successful.

If you want to control your FPS manually and make one key to switch between render and norender use this:
/bind X "toggle cg_norender 1 0"

It's not easy to do Strafe Jumps with it if you're not that trained, cause it's the same as jumping blind. But simple jumps where you just need to walk forward and jump should be possible for everyone to do.

Tutorial Details

Created: 4 years ago by ^THiNK#Jona

Views: 18502 Views

Keywords: Fps, increase fps, com_maxfps, show fps, improve fps, frames per second, call of duty fps, cod fps,

Share this Knowledge with your friends!

Direct Link:


I have wondered this: If you play with 200 gravity, you can fly with 1000 fps and you jump higher with 125 fps compared to 333. Why is it like that?

However, great tutorial Jona. :)
Commented by Jaska c(:[>*  (Dec 20th, 2013 01:07 PM)

The effects of those special FPS values are a result of rounding errors in the engines calculation system, this system is influnced by gravity and players jumpheight (jumpheight is fixed and never changes). The gravity cause a 800 units/second² of deceleration, and if you jump you're instantly given a vertical velocity of 270 units/second upwards. If you change the gravity now you have direct influence on this calculation system and that's why the effects also changes. At gravity 200 for example the deceleration is too low so it won't take you down with 500/1000 FPS, with gravity 10 it's even too low for any FPS value, with gravity 0 the deceleration is completly disabled.
Commented by ^THiNK#Jona  (Dec 20th, 2013 02:54 PM)

I got it, ty jona (happy)
Commented by Jaska c(:[>*  (Dec 20th, 2013 03:28 PM)

Awesome!!! :)
Commented by RustHy*  (Dec 20th, 2013 03:59 PM)

Is there something u dont know about that game jona? xD n1
Commented by ^m B ~ Valle  (Dec 27th, 2013 01:26 PM)

Jona The best (y)
Commented by MANTO ClsnGGGGGG  (Dec 27th, 2013 02:37 PM)

I have used the same bind but different keys looool. (/bind ' com_maxfps 76 to set 77 fps as I can't have 76 or 75, /bind [ com_maxfps 125 and /bind p com_maxfps 333 . That's impossible :D
Commented by ^Shad0W|Sniper  (Jan 04th, 2014 04:54 PM)

I wonder how few ppl can jump in a sequence in mp_brecourt. no-luck with Google... :/
Commented by $!l3nT K!ll3R  (Mar 18th, 2014 06:29 AM)

There you go: CoD1 Strafe Jumping Tutorial
It's about strafe bunny hopping.
Commented by ^THiNK#Jona  (Mar 18th, 2014 12:03 PM)

Gotcha. Looks easy though but need a lot of practice...
Commented by $!l3nT K!ll3R  (Mar 19th, 2014 10:58 AM)

What is meant by "noRender" "doRender".
I mean I did not completely understand the last part of tutorial.
Commented by $!l3nT K!ll3R  (Mar 19th, 2014 11:02 AM)

/seta noRender "com_maxfps 333; cg_norender 1"
It defines a script (squence of commands) with the name noRender.
The commands will set max fps to 333 and enable cg_norender which is a cvar that toggles rendering on and off.

/seta doRender "com_maxfps 125; cg_norender 0"
This is similar but sets fps back to original value and disables cg_norender.

/bind N "vstr noRender"
/bind M "vstr doRender"
vstr is used to execute such scripts we defined above.
In this case Press [N] = /vstr noRender = /com_maxfps 333; cg_norender 1
Commented by ^THiNK#Jona  (Mar 19th, 2014 06:49 PM)

This works as well for me, and u can just toggle it with the same key (n):

/bind n "toggle cg_norender 0 1; toggle com_maxfps 333 125"
Commented by ^m B ~ Valle  (Apr 06th, 2014 10:12 PM)

When i set render's value to 0 my fps reached 333 500 600 700 ... then my mouse were blocked :( anyone know wat is the solution
Commented by `RooKie~Haytham  (Aug 19th, 2014 10:45 AM)

If you set FPS above 1000 your mouse will freeze.
It's gone after restarting the game, simply don't go higher than 1000 FPS which is the max (useable) value of FPS
Commented by ^GotOwned.Jona#  (Aug 19th, 2014 02:03 PM)

Maybe someone can help me:
If I put 333fps I always get this "connection lost" sentence and marker at the screen, but my PC is just 1 year old and if i set 333fps he can keep them constantly at this lvl. If i set fps to 0 my PC got around 800fps on Carentan.. so dont think this can be a software problem or?
Or do I just have to deactivate this announcement of COD? Cause Jona wrote that its normal that a higher ping is showed with higher fps..
Commented by Thrain.  (Dec 11th, 2014 01:07 PM)

Sometimes i get huge fps drops to 150. Dont know if its ping releated
Commented by ^THiNK#Madness  (Dec 11th, 2014 02:25 PM)

Well I fixed it now.. the command /rate 25000 was missing it seems.. I added it and now I got constant 333fps, no matter which map.. :-)
So if u got the same problem and it shows u lags all the time, than try it with this command, maybe it works aswell for you :-)

Galvatron (former Thrain)
Commented by The real nuke Galvatron  (Dec 17th, 2014 02:11 PM)

I know this is a really old topic but Jona is there a way i can contact you about this?
Commented by ^GodLike`3tnieS..  (Jan 10th, 2015 12:10 PM)

don't try this - - > cg_norender 1
Commented by TheProTecTor{^ALi}  (Aug 10th, 2015 04:51 PM)

when i do cg_norender 1 the game is stop ,why?
Commented by Mafia  (Sep 20th, 2015 09:00 PM)

my laptop is samsung some people said to me it hasnt pc and when i look to the sky fps increase to 10 450 ??????????????
Commented by Mafia  (Sep 20th, 2015 09:03 PM)

10 , 450 not 10450
Commented by Mafia  (Sep 20th, 2015 09:04 PM)

????? ?? ???????
Commented by Mafia  (Sep 20th, 2015 09:07 PM)

dude.. there's nothing more normal.... That's what this command do ... it stops the game's rendering. In this way you get a high fps without the need to have a good pc. Even a pc that gets 20 fps can reach 333 fps easily using this way. What did u expect? lol
Commented by BEERemos  (Sep 20th, 2015 09:15 PM)

when i look up fps increase to 333 and when i look down decrease to 190 i want to be the same 333 fps what did i do?
Commented by Mafia  (Jan 27th, 2016 06:14 AM)

Significately decreases the pleasure? That's kinda pervert :P
Commented by |||||| def1  (Feb 05th, 2016 07:33 PM)

Please sign in or create an account to post a comment.