Hi folks.

Just finished Tomb Raider 1 and moved on to 2 only to find that the control scheme I'd been using in the first game doesn't work in this one. I noticed that any time I press the S key, the game slows to a crawl and is totally unplayable. A quick Google search turned up a conversation about how the S key is secretly bound to take screenshots, which would explain the slowdown.

So my question is whether anyone knows of a way to unbind the S key so that it can be used for normal WASD controls. Any files I could edit? Mods I could download? Or should I just skip to TR3?

I didn't have that problem when I played through the game a few years ago. I used the MultiPatch. Have you applied that?

http://www.tombraiderchronicles.com/tr2/fixes.html

You could also try the TR2 Updater:

http://www.tombraiderforums.com/showthread.php?t=217194

No luck there, sadly.

I did find a program called SharpKeys that allows me to effectively turn the S key into a different key, and then bind that key in TR2. Only issues are that it edits the Windows registry, which seems like overkill, and every time you want to turn it on or off, you have to restart the computer. Not an ideal solution... but it does work.

To do the same thing non-permanently, try AutoHotkey. You can create a simple script to change the behavior of the key, run the script before you start playing and then simply kill the script when you're done (or you can get fancier and have the script launch the game and automatically exit when the game exits).

AutoHotkey actually doesn't seem to work, unless I'm missing something. I remapped S to G and G to S, which works fine in Notepad, browser, etc. But in the game, I get some completely bizarre behavior. Pressing S (mapped to G) is now recognized by the game as BOTH keys I think. It causes me to step back but also totally freezes up the game for some reason. Pressing G (mapped to S) then unfreezes it. And both keys take screencaps.

There are two ways to map keys in AutoHotkey. The first is a straight 1-to-1 mapping:

s::g
g::s

Then, there's the more extensible way:

$s::send, {g}
$g::send, {s}

Try both of those and see if either solves the issue. FYI, the dollar signs might help prevent the double triggering.