Support Forum

Hey everyone, just decided to get a little Support FAQ going so people have at least a little bit of a better idea of how to make the FPS Mod work "most" of the time.

Okay, just some quick hints.
1) Read the existing instructions, I tried to explain as much as possible in there.
2) The control program doesn't have to be in any specific folder, in fact nothing is location specific, so even the map and everything else can be in different folders. (Unless stated otherwise in the instructions, sorry if I forget)
3) The control program works most of the time on it's own but very randomely, there are a few problems involved with this, one is that it searches for a 4byte section of memory, but it searches every 4 bytes
oooo|oooo|oooo
But if what it's looking for is displaced
oooo|oo12|34oo
Then it won't find the memory properly, this is a known bug and stoned who made the control program was too lazy to fix it >.<.

Other known bugs involve false positives which means it finds a piece of memory exactly like the one it's looking for and latches onto it falsely sometimes causing the game to crash when you press tab (when it starts chaning that memory) or just not working.

And sometimes it's a combination of the two, it misses the correct memory location and finds a false one. Anyways, this is why it fails, now here's how to make it work more often.

4) Okay tsearch is your best bet if it doesn't work often enough for your liking, and here's a few ways for you to weed out those false positives that it gives you. The tips are split into easy and difficult tips so if you don't know that much about memory and the way it works I'd stick to the easy ones.
Easy:
-Use the control program until it finds the right memory location and everything works, then write down the memory location it finds, and next time when it doesn't work and you decide to use tsearch look for similarity in the first few digits of what worked for you before and what tsearch gives you.
Difficult:
-The method that the control program uses to test if the memory location is correct is that it checks the 4 bytes after the found memory location and checks if the next 4 bytes make up the number 1, you can do this with each memory location that tsearch finds by double clicking on the memory location, and adding 4 to the number, if it's value becomes 1, you've got the right location

5) I have no idea what the camera problem involves but I'm guessing that it is connected with slow computers, it's simply that when the computer is slower than needed it won't be able to adjust the camera quickly enough so it slowly sinks, if you're having that problem try lowering your resolution/detail level

Woot! You posted!
Well, that's a good thing. At least we know undead zombies didn't eat your brain.

Maybe they did...maybe they did...