- Joined
- May 17, 2009
- Messages
- 8
This guide shows you what many players call the "Sweetspot". You hit where you aim alot more often. It should work for most people. Before doing this, you should tweak your graphics settings to make the game run at a constant framerate. I'll just say that you need a consistent framerate to use this. Try lowering your resolution, antialiasing, and dynamic lights. Also, try messing with your driver settings, but I'll warn you ahead of time. If you're unfamiliar with your graphics driver settings, changing random stuff can cause way more problems than they fix. If you want to tweak your game to the maximum that it can be tweaked, check the link at the bottom. It has way more indepth information for all Quake Engine Games.
Ok, so to do this, you need to first know how to use your console. Hit the ~ key, or hold shift and hit the ~ key for the full console. Other than that, there are 4 settings you need to know about.
/cg_drawlagometer 1
/cg_drawfps simple
/com_maxfps ??
/cl_maxpackets ??
First you drop your console and type "/cg_drawfps simple" and "/cg_drawlagometer 1" without the " ".
After playing a couple maps, mainly Creek, Downpour, and Countdown, you should have a good idea of your framerate. (I have to make a note in here. Don't worry if you only get 60fps. As long as the game is smooth, you're good.) If you're not playing CoD4, just play a few maps with alot of smoke, running water, or large maps in general. Figure out your worst sustained framerate (the top numbers, not the cg/ms one). By that I mean, if your frames hold steady at 60fps on Creek, and 90 on Chinatown, and 65 on Downpour, yours would be 60. After you have that figured out, you can then use the other 2 commands. Also, watch your netgraph. The little box in the bottom right hand corner. The top, blue line is the incoming data, which you have no control over, and the bottom, green line, which is the outgoing data. This one will show red, black and yellow lines from time to time. I'll explain more later.
Ok, now the fun part. You want to set your /com_maxfps to your worst sustained fps (in the above example, it'd be "/com_maxfps 60) and then set your /cl_maxpackets to a few points above (again, in my example, you'd set it to /cl_maxpackets 62). The max packets will round down to the nearest valid number. Ok, now is the time to watch your netgraph and ping. You should see a big difference in your netgraph, like less bumps, or less black and/or red lines. As you optimize your settings, you may also see the green bar (your outgoing data) get smaller and smoother. You should see what I mean. If you spec me on the MD server, you'll see that my netgraph is a nice smooth line.
So, you may have to tinker with it a bit, but in the end, it's worth it.
For more info, and some technical stuff on this, check out Bash'nSlash's blog on the Quake engine
I'll put these in here just in case you all want an easy fix
1. Given: Com_MaxFPS = 125
Best value for Cl_MaxPackets = 125
2. Given: Com_MaxFPS = 76
Best value for Cl_MaxPackets = 77
3. Given: Com_MaxFPS = 111
Best value for Cl_MaxPackets = 112,
4. Given: Com_MaxFPS = 71
Best value for Cl_MaxPackets = 72
5. Given: Com_MaxFPS = 55
Best value for Cl_MaxPackets = 56
Mine I set to cl_maxpackets 50 and com_maxfps 100
still a nice smooth line, with 1 packet sent for every 2 frames.
Have Fun,
Je'la'd
Ok, so to do this, you need to first know how to use your console. Hit the ~ key, or hold shift and hit the ~ key for the full console. Other than that, there are 4 settings you need to know about.
/cg_drawlagometer 1
/cg_drawfps simple
/com_maxfps ??
/cl_maxpackets ??
First you drop your console and type "/cg_drawfps simple" and "/cg_drawlagometer 1" without the " ".
After playing a couple maps, mainly Creek, Downpour, and Countdown, you should have a good idea of your framerate. (I have to make a note in here. Don't worry if you only get 60fps. As long as the game is smooth, you're good.) If you're not playing CoD4, just play a few maps with alot of smoke, running water, or large maps in general. Figure out your worst sustained framerate (the top numbers, not the cg/ms one). By that I mean, if your frames hold steady at 60fps on Creek, and 90 on Chinatown, and 65 on Downpour, yours would be 60. After you have that figured out, you can then use the other 2 commands. Also, watch your netgraph. The little box in the bottom right hand corner. The top, blue line is the incoming data, which you have no control over, and the bottom, green line, which is the outgoing data. This one will show red, black and yellow lines from time to time. I'll explain more later.
Ok, now the fun part. You want to set your /com_maxfps to your worst sustained fps (in the above example, it'd be "/com_maxfps 60) and then set your /cl_maxpackets to a few points above (again, in my example, you'd set it to /cl_maxpackets 62). The max packets will round down to the nearest valid number. Ok, now is the time to watch your netgraph and ping. You should see a big difference in your netgraph, like less bumps, or less black and/or red lines. As you optimize your settings, you may also see the green bar (your outgoing data) get smaller and smoother. You should see what I mean. If you spec me on the MD server, you'll see that my netgraph is a nice smooth line.
So, you may have to tinker with it a bit, but in the end, it's worth it.
For more info, and some technical stuff on this, check out Bash'nSlash's blog on the Quake engine
I'll put these in here just in case you all want an easy fix
1. Given: Com_MaxFPS = 125
Best value for Cl_MaxPackets = 125
2. Given: Com_MaxFPS = 76
Best value for Cl_MaxPackets = 77
3. Given: Com_MaxFPS = 111
Best value for Cl_MaxPackets = 112,
4. Given: Com_MaxFPS = 71
Best value for Cl_MaxPackets = 72
5. Given: Com_MaxFPS = 55
Best value for Cl_MaxPackets = 56
Mine I set to cl_maxpackets 50 and com_maxfps 100
still a nice smooth line, with 1 packet sent for every 2 frames.
Have Fun,
Je'la'd
Last edited:
