lol, you just took this from AlterIW but nice guide anyway.
The four commands follow:
com_maxfps: This command control your FPS cap limit. This command is best set at "0" to remove any limit; freeing your graphics card to load as many frames as it can.(Should have vSync off as well) Some players like to set it to 100, but it would be better just to have it run freely instead of capped.
cl_maxpackets: This command is probably the best when it comes to hit registration and how often you update your position to the host/server. (there was this theory called the "sweetspot," that used to work, but doesn't work now so don't try to set it to 125. It won't work.) This command is best set at 100(max).
Snaps: This command can help with how often you receive updates from the server. Setting this to 30(max) will allow you to get more up-to-date player positions and events happening on the server.
cl_packetdup: This command has a impact on bandwidth and latency. What it does is send two copies of one packets to a host/server to help guarantee the server receives it. On a good connection it is best to set this to 0 so you don't send twice or even triple the amount of bandwidth worth of packets at the same time. It will allow for more frequent packet outputs and less bandwidth usage. On a bad connection with frequent packet drops/lossage it is best to set this to 1-5.(use trial-and-error to find what works best for you.)
This concludes my Client part.
For those who like to host or force host(party_connecttimeout 1). This one command right here can probably be your best friend.
Sv_network_fps: This controls how many Frames(updates) your CPU is allowed to make per second, it is also dependent on the GPU as well(don't ask why.) This setting is at a default of 50 for most average computers this is good, but for people with quad cores(Core 2 Qaud, Core i3, i5, and i7, or even AMD's Triple and Quad core setups) this is best set at 1000. Why so high? The higher the rate, the more updates, meaning when you send a player a update(packet) it will be the MOST recent update, allowing for the player to have better hit reg and less lag. This command requires com_maxfps to be at 0 or it will be useless.
Thanks for reading and happy playing or hosting.
lol, you just took this from AlterIW but nice guide anyway.
Donate:
BTC: 1GEny3y5tsYfw8E8A45upK6PKVAEcUDNv9
Handy Tools/Hacks:
Extreme Injector v3.7.3
A powerful and advanced injector in a simple GUI.
Can scramble DLLs on injection making them harder to detect and even make detected hacks work again!
Minion Since: 13th January 2011
Moderator Since: 6th May 2011
Global Moderator Since: 29th April 2012
Super User/Unknown Since: 23rd July 2013
'Game Hacking' Team Since: 30th July 2013
--My Art--
[Roxas - Pixel Art, WIP]
[Natsu - Drawn]
[Natsu - Coloured]
All drawings are coloured using Photoshop.
--Gifts--
[Kyle]
It truly is a nice (yet already known) guide, but for some reason it still doesn't help me solving my EXE_HOSTUNREACH problem -.-
Is there a way to edit them without a console ?
Maybe edit the config_mp.cfg inside the "players" folder ? If yes, which lines ?
Open with WordPad. Ctrl+F. Win.
does anyone report any improvements with this? ive done the aIW tut and the last line for this tut. im not shure if there is any difference cuz my laptop hold mw2 fairly well.
nice i never have thought of that
I Am on this site for the mods for mw2 ONLY. Not hacks.
this is more of an tutorial
/moved