Written by jockyitch Wednesday, 23 April 2008 UPDATED: Apr 2008 The yitch2 configuration came out during the Christmas season of 2007 and it was quite a hit. CoD4 Tweaks: The yitch3 configuration Written. Coming up with yitch1.cfg and yitch2.cfg CoD4 multiplayer config files was relatively easy. Yitch configs.

• Cod Waw Yitch
• Yitch3 Config Cod4

CoD4 Tweaks: The yitch3 configuration Written by jockyitch Thursday, 15 May 2008 Welcome to BASHandSlash.com Many of you have come here because of the so-called 'yitch3' CoD4 MP configuration file. That config is downloadable below. If you are new to using config files, please read this:. Hopefully you will find it a good jumping-off point for your own configs. We have tried to provide as much information as possible for you to create your own configs on this site. Have a look at the following where we have noted down many of the dvars we have used in this config.

Also, if you want to test out your config file, I suggest you have a read of this. Don't forget to look around the site, we have quite a few articles to help you play better and if you have time, don't forget to check out our CoD Webcast,.jock ORIGINAL ARTICLE 2008-05-14 Ted Cargill from Bell Labs used to say. Background In retrospect, coming up with and CoD4 multiplayer config files was relatively easy.

After all, yitch1 was made by ostensibly copying and moderately tweaking a configuration made for slow computer systems that was included in the CoD4 DVD by an IW staffer known as. BASHandSlash.com spoke to this IW employee this week and we asked him about his now famous configuration. Apparently, the dk05.cfg file was concocted as a result of the fact that dk05 had a sluggish computer and wanted to run CoD4 with as high a frame-rate as possible. The other interesting fact we learned was that the config should never have been on the DVD! It was accidentally copied to the master - and that's how we got it. The rest is history. Of course, we here at BASHandSlash.com thanked dk05 for his config file.heck, without his efforts many of us in CallofDutyville with slug-computers would have been S.O.L.

When it came to CoD4. What is the yitch3.cfg file?

In our opinion, CoD4's configmp.cfg file plays a huge role in the outcome of online gaming. More accurately, the role is huge.if.

your system (hardware and communication systems) is bottlenecked. FPS rate is life online and if your system cannot attain the same framerates as your opponents, you will find yourself more often than not.dead. Note that we were running a different Forceware driver set than was used when we came up with yitch2.

For that reason, the yitch2 frame rate is lower than that reported in the original yitch2 article. The absolute FPS is not that important - we are just looking for relative improvement over stock. Either way, yitch3 yields an FPS almost a factor of 4 higher than stock. Firstly, we have sweet-spotted fps/packets/snaps/rate comms combo so that (hopefully) you will find better registration.

The fps has been capped at 125 (commaxfps) and uploads to the server have been set at 42 (this latter value would probably be best set at clmaxpackets '63'; however, folks with low end systems have found a slightly beneficial ping at 42.we've left it there). We have added a few binds for you below to modify these values as you see fit. Does yitch3 give you an FPS boost?

But it is a small increase over yitch2. On our system it gave us roughly 10% in certain situations.

What is new in yitch3 is to provide you with toggle and preset binds to allow you to change your config on the fly. In this way if a server kicks you for having lowish settings.you can instantly crank them up to meet the minimum requirements.

Toggles One of the biggest complaints with the yitch1 and 2 configs was that PunkBuster would kick you if your config was outside the bounds set by the server admins. In yitch2, you could get kicked from a server (NOT banned.just kicked temporarily), if say, your picmip setting was 3 (low res), or for setting lodscale to a low res setting. Bind F7 'toggle rlodscalerigid 3 2 1 4.

Bind KPHOME 'commaxfps 66; clmaxpackets 34' - Sweet spot setting used to optimize server connection. FPS is capped here at 66. For those that can only achieve a constant 66 fps rate, use this setting. Bind KPUPARROW 'commaxfps 76; clmaxpackets 39' - Sweet spot setting used to optimize server connection. FPS is capped here at 76.

For those that can only achieve a constant 76 fps rate, use this setting. Bind KPPGUP 'exec stock.cfg; //rapplypicmip. Seta cghudGrenadeIconWidth '40' seta cghudGrenadePointerHeight '40' - slightly increased size of nade indicator seta cgmarks '0' seta cgmarksentsplayeronly '0' - do not show bullet holes seta clmaxpackets '42' seta commaxfps '125' - capped FPS to 125 and set maxpackets to a 'sweet spot' value. Should provide lowest ping and a 9% increase in jump height over standard stock settings.

Seta cltimeNudge '-15' - we are unsure if this command is supported in CoD4. But have added this Quake command as a registration placebo.

Seta coninputBoxColor '0.15 0.2 0.4 0.7' seta coninputHintBoxColor '0.15 0.2 0.4 0.7' - made console input box slightly translucent (now you can still see FPS indicator thru it). Seta hudfadehealthbar '0' seta hudfadeoffhand '0' seta hudfadesprint '0' seta hudfadestance '0' - stops hud from fading as in yitch2 (negligible FPS hit). Seta rcachemodellighting '1' seta rcachesmodellighting '1' - should provide FPS boost seta rpicmipwater '0' - no water reflections seta rtexFilterAnisoMax '1' seta rtexFilterAnisoMin '1' - bare minimum anisotropic filtering seta snaps '30' - increased ping a bit, but hopefully increased registration with this server packet setting seta waypointiconheight '15' seta waypointiconwidth '15' - bomb site icons now much smaller to improve visibility. BACKUP your current configmp.cfg file first!

Copy paste yitch3.cfg into configmp.cfg between your binds and the conhidechannel command line. Note that yitch3 over-rides most F-key binds and KeyPad binds.

Check that your binds have not been over-ridden. Write-protect the configmp.cfg file. Problems Report issues in our forums (do not e-mail us): Credits These config files are a community effort.

The thank you's start with dk05 from IW. We then go to the forum-goers at GotFrag.com (especially scot).

Finally, we ask for a standing ovation to the great forum posters of BASHandSlash.com: Doctor of Quake engine configurations DAFlash, puller, FoX and Volatile. Thank you guys, and anyone else I may have missed, for providing the insight into this configuration file.

Background In retrospect, coming up with and CoD4 multiplayer config files was relatively easy. After all, yitch1 was made by ostensibly copying and moderately tweaking a configuration made for slow computer systems that was included in the CoD4 DVD by an IW staffer known as. BASHandSlash.com spoke to this IW employee this week and we asked him about his now famous configuration.

Apparently, the dk05.cfg file was concocted as a result of the fact that dk05 had a sluggish computer and wanted to run CoD4 with as high a frame-rate as possible. The other interesting fact we learned was that the config should never have been on the DVD! It was accidentally copied to the master - and that's how we got it. The rest is history. Of course, we here at BASHandSlash.com thanked dk05 for his config file.heck, without his efforts many of us in CallofDutyville with slug-computers would have been S.O.L.

When it came to CoD4. What is the yitch3.cfg file? In our opinion, CoD4's configmp.cfg file plays a huge role in the outcome of online gaming. More accurately, the role is huge.if. your system (hardware and communication systems) is bottlenecked. FPS rate is life online and if your system cannot attain the same framerates as your opponents, you will find yourself more often than not.dead. Note that we were running a different Forceware driver set than was used when we came up with yitch2.

For that reason, the yitch2 frame rate is lower than that reported in the original yitch2 article. The absolute FPS is not that important - we are just looking for relative improvement over stock. Either way, yitch3 yields an FPS almost a factor of 4 higher than stock. Firstly, we have sweet-spotted fps/packets/snaps/rate comms combo so that (hopefully) you will find better registration. The fps has been capped at 125 (commaxfps) and uploads to the server have been set at 42 (this latter value would probably be best set at clmaxpackets '63'; however, folks with low end systems have found a slightly beneficial ping at 42.we've left it there).

We have added a few binds for you below to modify these values as you see fit. Does yitch3 give you an FPS boost? But it is a small increase over yitch2. On our system it gave us roughly 10% in certain situations. What is new in yitch3 is to provide you with toggle and preset binds to allow you to change your config on the fly. In this way if a server kicks you for having lowish settings.you can instantly crank them up to meet the minimum requirements.

Toggles One of the biggest complaints with the yitch1 and 2 configs was that PunkBuster would kick you if your config was outside the bounds set by the server admins. In yitch2, you could get kicked from a server (NOT banned.just kicked temporarily), if say, your picmip setting was 3 (low res), or for setting lodscale to a low res setting. Bind F7 'toggle rlodscalerigid 3 2 1 4. Bind KPHOME 'commaxfps 66; clmaxpackets 34' - Sweet spot setting used to optimize server connection. FPS is capped here at 66. For those that can only achieve a constant 66 fps rate, use this setting.

Bind KPUPARROW 'commaxfps 76; clmaxpackets 39' - Sweet spot setting used to optimize server connection. FPS is capped here at 76. For those that can only achieve a constant 76 fps rate, use this setting. Bind KPPGUP 'exec stock.cfg; //rapplypicmip. Seta cghudGrenadeIconWidth '40' seta cghudGrenadePointerHeight '40' - slightly increased size of nade indicator seta cgmarks '0' seta cgmarksentsplayeronly '0' - do not show bullet holes seta clmaxpackets '42' seta commaxfps '125' - capped FPS to 125 and set maxpackets to a 'sweet spot' value.

Should provide lowest ping and a 9% increase in jump height over standard stock settings. Seta cltimeNudge '-15' - we are unsure if this command is supported in CoD4. But have added this Quake command as a registration placebo. Seta coninputBoxColor '0.15 0.2 0.4 0.7' seta coninputHintBoxColor '0.15 0.2 0.4 0.7' - made console input box slightly translucent (now you can still see FPS indicator thru it). Seta hudfadehealthbar '0' seta hudfadeoffhand '0' seta hudfadesprint '0' seta hudfadestance '0' - stops hud from fading as in yitch2 (negligible FPS hit). Seta rcachemodellighting '1' seta rcachesmodellighting '1' - should provide FPS boost seta rpicmipwater '0' - no water reflections seta rtexFilterAnisoMax '1' seta rtexFilterAnisoMin '1' - bare minimum anisotropic filtering.

BACKUP your current configmp.cfg file first! Copy paste yitch3.cfg into configmp.cfg between your binds and the conhidechannel command line.

Cod Waw Yitch

Note that yitch3 over-rides most F-key binds and KeyPad binds. Check that your binds have not been over-ridden. Write-protect the configmp.cfg file.

Yitch3 Config Cod4

Problems Report issues in our forums (do not e-mail us): Credits These config files are a community effort. The thank you's start with dk05 from IW. We then go to the forum-goers at GotFrag.com (especially scot). Finally, we ask for a standing ovation to the great forum posters of BASHandSlash.com: Doctor of Quake engine configurations DAFlash, puller, FoX and Volatile.

Thank you guys, and anyone else I may have missed, for providing the insight into this configuration file. Source: Category: Added by: (2009-03-09) Author: jockyitch Views: 660 Rating: 0.0/ 0 Total comments: 0.