Tips 'n Tricks: Left 4 Dead

If you've noticed that your Left 4 Dead has an annoying static-ity sound whenever the playback sound for fire is rolling, here's what to type into the console: "snd_rebuildaudiocache". You will be brought to a loading screen where the game takes approximately 5 mins to rebuild the audio cache. After the loading screen disappears, the problem will likely be fixed.

This pervasive annoyance has been present ever since I updated to version 1.0.1.3. It forces me to turn down the volume since the crackling static sound envelopes all other sounds. As such, I have to rely on my two eyes to aid me in slaying the waves of infected people. Believe me, this is particularly disadvantageous in the presence of a Witch. In fact I've been waiting for a fix for weeks now, and finally, I now have it.

Also, here's a bunch of other console commands to play as the infected (without humans controlling any of the survivors). This is predominately practical if you want to brush up some of your infected skills (as did I) or if you simply want to hunt down the survivors alone.

"sv_cheats 1
sb_all_bot_team 1
sb_unstick 0
vs_max_team_switches 99
mp_gamemode versus"

After entering the above lines of code, press the change team key to switch to the infected team. A word of caution: I've tried it and do note that the AI controlled survivors can fly through the levels pretty swiftly. So it's probably best if you increase the game's difficulty. However, they can get stuck pretty often. For instance, they don't seem to be able to activate switches. Also, they can foolishly get stuck scaling a ladder when an infected is already on the ladder above them. If this happens, you can rejoin the survivors team, get the obstacle out of their path, then quickly swap back to the infected team.

For a complete list of console commands, visit http://left4dead.wikia.com/wiki/Complete_list_of_console_commands.

After months of playing, Left 4 Dead is still fun :D
T'ang

Falcon Guard

I have successfully installed MechWarrior 2 on Windows XP last week. Gosh, the process sure was wearisome. I tried quite a few methods but none of them seemed to work, save for the last one. I'll get to what method I used later.

Memories rushed back as soon as I launched my first instant action mission in eons. I have completed the Jade Falcon Clan's campaign in a mere 2 days. Though gratifying at first, the game soon lost it's re-play value, partly due to odd anomalies that appeared. But before I go on, let me show you some screenshots of an in-game session to prove that the game mostly does work:

external view of the Timber Wolf Mech

with "image enhancement" engaged

cockpit view

What made the installation process so depressing is that I couldn't find a method that appealed to my version of MechWarrior 2. You see, there are close to 36 versions of MechWarrior 2 that have been produced to date (not to mention two separate DOS and Windows versions), and not all versions share the same installation methodology on XP. My version is pretty rare as mine came bundled with the Microsoft SideWinder Pro joystick. It would seem rational to assume that most gamers bought or will buy the retail copy MechWarrior 2, and only a handful acquire the game through a joystick bundle. As such, most installation guides were only appropriate for retail versions. Providentially, I managed to decipher that mine was a non-retail Windows Pentium edition, and I found a installation guide just for it. If anyone's interested, here's the link to the guide I used.

the disc of a MechWarrior 2 version similar to mine
(Credit: Mech2.org)

Now, to the oddities. Perhaps the most infuriating problem is that some of the missiles fired from Mechs explode upon their departure from the rocket pods, thus inflicting self-damage. This is particularly maddening as before you can complete a mission, chances are you have already blown yourself to bits. This forces you to use Mechs that do not include missiles as part of its arsenal. I'm afraid this leaves you with very few Mechs. Strangely (and fortunately), the Timber Wolf Mech does not suffer from this eccentricity. I soon got tired piloting the same few Mechs over and over again. I read up on mech2.org, a site dedicated to MechWarrior 2, that this quirk is a result of the game being run on too advanced systems. Running the game on modern computers causes the frame rate to peak so high that it causes missiles to explode instantaneously upon their launch. Weird, huh. I've heard of games not functioning optimally due to incapable systems, but also on over-capable ones too?

Additionally, the blue pixels mysteriously changes to white after a few minutes of gameplay. Though this isn't much of a hindrance.

I know that I am lucky enough to get the supposedly Windows 95/98-only game working on XP and I'm just nitpicking on minor glitches. Still, no matter how unlikely it would seem, it will make my day if these hiccups be mended one day.

T'ang