Alot of people have problems with there framerate in games and there has been a program released a while back, but with limited information about it, and with a ton of problems that people can seem to get around. I have been fooling around with this program for a while and have eliminated all of the possible bugs/problems that other people have had. In order for you to achieve 100% results, follow every instruction CAREFULLY.

This topic is basically to clear up any questions and answers that everyone has about how this program works and how to get it functionally working.

Question 1 - Why would you want to "limit" your framerate?

Answer - Limiting the framerate for your games is basically to achieve the best "consistent" framerate for your games. This means that things like framerate spikes (large FPS drops or gains during games that can typically annoy the common person) will be either extremely reduced to the point where you wont even notice it, or completely eliminated. Both of these results are based on what kind of machine you are running, and what games you're playing.

Question 2 - What does it mean to "limit" your framerate?

Answer - Game performance has been the PC gamer topic every since games were invented. It is the pinnacle point between quality and performance of what type of balance you will get for your games. Essentially, the human eye is very effecient in spotting the differences between high and low framerates, for example, if your playing a game, and the FPS is in the high 60's (the best consistently smooth framerate for 60hz Monitors) and drops to the low 30's or even 20's, the human eye will immidiately detect that there isnt a smooth picture anymore.

Question 3 - Does lower framerate mean less of a smooth moving picture?

Answer - Yes it does. However, the human eye is very unique in a way where it can adapt to certain rates of images. For example, if there is a consistant 30fps (Frames Per Second) in front of you, your eye is more likely to be comfortable with that then if your framerate is increasing and decreasing every second for random periods of time. Console games today use 2 common framerate caps - 30fps and 60fps. These framerate caps are put in place for this very reason - to have consistent framerates through your gamig experience.

Question 4 - What are the limits of what is considered consistent and what is not?

Answer - The most common FPS locks are basically any number above 30, but with multiples of 5 or 10. So 35, 40, 45, 50 and even 55 are the numbers to hit for best results. Keep in mind, this concept of limiting your FPS is strictly LIMITING your framerate, as you cannot add framerates that you could not get in the first place.

The steps listed below will guide you from start to finish on how to cap your framerates in your games.

==========================================================================================

Step 1 - Download the link below:

http://rapidshare.com/files/160642187/FPS_Limiter_0.2.rar

Step 2 - Extract the file anywhere you like, but make sure that the place where you put it, will be its PERMENANT location (this is to eliminate directory path problems in the future).

Step 3 - Run the file in the folder that you just extracted, called "FPS_Limiter_GUI.jar", DO NOT run the "FPS_Limiter.exe" file, it will not work.

Step 4 - When you have the program running in front of you, you will need to browse to the root location of the executable file of the game of your choosing. (NOTE: Games that already have an automatic 30fps cap cannot be increased any higher, so it is pointless to select these games)

Step 5 - Once you have the game's DIRECT executable chosen, select from one of the 3 in the dropdown list at the menu at the top of the screen.

D3D8 - DirectX 8 games

D3D9 - DirectX 9 games

OGL - OpenGL games (very few games run with the OpenGL language)

Step 6 - Once you have selected either D3D8/D3D9/OGL, then select which framerate you want the game to lock at at the "maximum fps" box. For best results, if your lowest framerate is under 30, select a number that is 5-10 fps above for that specific game. If your framerate is above 30, select any number between 30 to 50. Experiment with it a little, you can always change your framerate lock.

Step 7 - Once you've selected your Maximum FPS, click on "create bat" to make a .bat file in the FPS Limiter folder.

Step 8 - When you're ready to play, double click on that .bat file. If you wish to make a shortcut, right click on the .bat file and select "Create Shortcut". You can change the name of the shortcut ONLY, do not change the name of the .bat file.

NOTE: To change your Maximum FPS setting without repeating the whole process, right click on the .bat file created, and go to edit. Now find the line that says "/f:X" replace the "X" variable with whatever you like.

FOR ATI USERS ONLY - ATI Tray Tools or any other 3rd Party Driver software cannot be run while using FPS Limiter. I am not sure how the program reacts with Nvidia 3rd Party Drivers, but it is recommended that you disable it before continuing.

Here is a list of games that I personally own and have tested that work with the program:

NOTE #1 -A

Left 4 Dead for PC's Splitscreen function supports a very flexible amount of console commands, in which specificly controls can be customized to either work on keyboard or joystick, but in this case, Xbox 360 controllers.

This post will teach you how to use BOTH Keyboard/Mouse and Xbox 360 Controllers in SPLITSCREEN mode.

POST SCRIPT: THIS IS ONLY FOR CONTROLLER CONFIGURATION, THIS IS NOT INSTRUCTIONS ON HOW TO PLAY SPLITSCREEN MODE.

STEP 1: Start up Left 4 Dead

STEP 2: Open up the console (tilde key/ to enable it, go to options)

STEP 3:

METHOD 1: Copy all of the given text for whichever specific type of controls you want, into the console command.

METHOD 2: Copy the ENTIRE text in a ".cfg" file, and save that file into your" \Left 4 Dead\left4dead\cfg\" folder, and name it "SPLITSCREEN_2_XBOX 360_CONFIG.cfg"

STEP 4: For METHOD 2, after saving and naming that file into the directory, run Left 4 Dead again and type "exec SPLITSCREEN_2_XBOX 360_CONFIG.cfg"

STEP 5: Both Xbox 360 Controllers plugged in (both wireless and wired work) should have 100% functionality with the DEFAULT GIVEN CONFIG.

TIP : Below, the given scripts either start off with "cmd1" or "cmd2". These lines are very important, and they differentiate between PLAYER 1 (cmd1) and PLAYER 2 (cmd2). They can be played around with, but be sure to make backups just in case.

HOW TO CHANGE YOUR CONTROLLER SENSITIVITY/LOOK SETTINGS:

The following lines are found in the given scripts. These 2 specific lines change the sensitivity of the right analog stick for the Xbox 360 Controller.

Depending on your taste, lower or increase the values by 0.1 decimals at the least (0.2, 0.3, 0.4, 0.5 etc), and 1.0 values at the most (1.0, 2.0, 3.0, 4.0 etc). ALWAYS REMEMBER, if you want to change the 1st ID tag player, than use the "cmd1" line, and if you want to change the 2nd ID tag palyer, then use the "cmd2" line.

(The negative value of the yaw sensitivity should not be removed, as it will not function properly if so).

cmd1 joy_pitchsensitivity "2.0";
cmd1 joy_yawsensitivity "-3.0";

cmd2 joy_pitchsensitivity "2.0";
cmd2 joy_yawsensitivity "-3.0";

==============================================================================================================

FOR 2 XBOX 360 CONTROLLERS INPUT:

===========================

joy_variable_frametime 1;
joy_autoaimdampenrange 0.85;
joy_autoaimdampen 0.5;
joy_lowend 0.65;
joy_lowmap 0.15;
joy_accelscale 3.0;
joy_accelmax 4.0;
joy_response_move 5;
joy_response_look 1;
joy_autoaimdampen 0.3;
joy_autoaimdampenrange 0.85;
joyadvancedupdate; // advanced joystick update allows for analog control of move and look
cmd1 +jlook;
cmd1 joy_pitchsensitivity "2.0";
cmd1 joy_yawsensitivity "-3.0";
cmd1 bind "A_BUTTON" "+jump;+menuAccept";
cmd1 bind "B_BUTTON" "+reload";
cmd1 bind "X_BUTTON" "+use";
cmd1 bind "Y_BUTTON" "lastinv";
cmd1 bind "R_TRIGGER" "+attack";
cmd1 bind "L_TRIGGER" "+attack2";
cmd1 bind "R_SHOULDER" "+lookspin";
cmd1 bind "L_SHOULDER" "toggle_duck";
cmd1 bind "STICK1" "vocalize smartlook";
cmd1 bind "STICK2" "+zoom";
cmd1 bind "BACK" "togglescores";
cmd1 bind "START" "pause";
cmd1 bind "S1_UP" "+menuUp";
cmd1 bind "S1_DOWN" "+menuDown";
cmd1 bind "UP" "impulse 100";
cmd1 bind "LEFT" "slot3";
cmd1 bind "RIGHT" "slot4";
cmd1 bind "DOWN" "slot5";
cmd2 +jlook;
cmd2 joy_pitchsensitivity "2.0";
cmd2 joy_yawsensitivity "-3.0";
cmd2 bind "A_BUTTON" "+jump;+menuAccept";
cmd2 bind "B_BUTTON" "+reload";
cmd2 bind "X_BUTTON" "+use";
cmd2 bind "Y_BUTTON" "lastinv";
cmd2 bind "R_TRIGGER" "+attack";
cmd2 bind "L_TRIGGER" "+attack2";
cmd2 bind "R_SHOULDER" "+lookspin";
cmd2 bind "L_SHOULDER" "toggle_duck";
cmd2 bind "STICK1" "vocalize smartlook";
cmd2 bind "STICK2" "+zoom";
cmd2 bind "BACK" "togglescores";
cmd2 bind "START" "pause";
cmd2 bind "S1_UP" "+menuUp";
cmd2 bind "S1_DOWN" "+menuDown";
cmd2 bind "UP" "impulse 100";
cmd2 bind "LEFT" "slot3";
cmd2 bind "RIGHT" "slot4";
cmd2 bind "DOWN" "slot5";

==============================================================================================================

MIXED KEYBOARD/MOUSE AND XBOX 360 CONTROLLER INPUT

For this type of setup, you must have the Xbox 360 controller on the "2nd" ID tag, in order for it to work.

However, if you cant get it to work, then you must manually change the Xbox 360 controllers config settings - if the line is "cmd1", then change it to "cmd2". If you do this, then you must also change the keyboard/mouse config settings to the opposite ID tag.

==============================================================================================================

FOR 1 XBOX 360 CONTROLLER AND 1 KEYBOARD/MOUSE:

========================================

cmd1 bind "0" "slot10";
cmd1 bind "1" "slot1";
cmd1 bind "2" "slot2";
cmd1 bind "3" "slot3";
cmd1 bind "4" "slot4";
cmd1 bind "5" "slot5";
cmd1 bind "6" "slot6";
cmd1 bind "7" "slot7";
cmd1 bind "8" "slot8";
cmd1 bind "9" "slot9";
cmd1 bind "a" "+moveleft";
cmd1 bind "c" "+voicerecord";
cmd1 bind "d" "+moveright";
cmd1 bind "SPACE" "+use";
cmd1 bind "f" "impulse 100";
cmd1 bind "h" "motd";
cmd1 bind "m" "chooseteam";
cmd1 bind "q" "lastinv";
cmd1 bind "r" "+reload";
cmd1 bind "s" "+back";
cmd1 bind "t" "impulse 201";
cmd1 bind "u" "messagemode2";
cmd1 bind "w" "+forward";
cmd1 bind "x" "+mouse_menu QA";
cmd1 bind "y" "messagemode";
cmd1 bind "z" "+mouse_menu Orders";
cmd1 bind "`" "toggleconsole";
cmd1 bind "MOUSE3" "+jump";
cmd1 bind "TAB" "+showscores";
cmd1 bind "ESCAPE" "cancelselect";
cmd1 bind "SHIFT" "+speed";
cmd1 bind "c" "+duck";
cmd1 bind "F1" "Vote Yes";
cmd1 bind "F2" "Vote No";
cmd1 bind "F5" "jpeg";
cmd1 bind "MOUSE1" "+attack";
cmd1 bind "MOUSE2" "+attack2";
cmd1 bind "e" "+zoom";
cmd1 bind "MWHEELUP" "invprev";
cmd1 bind "MWHEELDOWN" "invnext";

joy_variable_frametime 1;
joy_autoaimdampenrange 0.85;
joy_autoaimdampen 0.5;
joy_lowend 0.65;
joy_lowmap 0.15;
joy_accelscale 3.0;
joy_accelmax 4.0;
joy_response_move 5;
joy_response_look 1;
joy_autoaimdampen 0.3;
joy_autoaimdampenrange 0.85;
joyadvancedupdate; // advanced joystick update allows for analog control of move and look
cmd2 +jlook;
cmd2 joy_pitchsensitivity "2.0";
cmd2 joy_yawsensitivity "-3.0";
cmd2 bind "A_BUTTON" "+jump;+menuAccept";
cmd2 bind "B_BUTTON" "+reload";
cmd2 bind "X_BUTTON" "+use";
cmd2 bind "Y_BUTTON" "lastinv";
cmd2 bind "R_TRIGGER" "+attack";
cmd2 bind "L_TRIGGER" "+attack2";
cmd2 bind "R_SHOULDER" "+lookspin";
cmd2 bind "L_SHOULDER" "toggle_duck";
cmd2 bind "STICK1" "vocalize smartlook";
cmd2 bind "STICK2" "+zoom";
cmd2 bind "BACK" "togglescores";
cmd2 bind "START" "pause";
cmd2 bind "S1_UP" "+menuUp";
cmd2 bind "S1_DOWN" "+menuDown";
cmd2 bind "UP" "impulse 100";
cmd2 bind "LEFT" "slot3";
cmd2 bind "RIGHT" "slot4";
cmd2 bind "DOWN" "slot5";

Unfortunately, since the keyboard ID tag cannot be changed, as all keyboards are read from ID tag 1, that means that you cannot have 2 keyboard inputs at any time.

I've been looking all over the web for a way to limit FEAR games framerate for smoother performance. I've "accidentally" discovered a nice little command that I typed into the "autoexec.cfg" file.

Step 1: Open your F.E.A.R. game folder to where you installed it - I've tested it with ALL FEAR GAMES, IT WORKS.

Step 2: Find the "autoexec.cfg" file, open it up with Notepad (you can either rename it or double click and set it to default open with Notepad).

Step 3: You should see this line - (without the quotes)

"DisableMaterialsFromFile 1"

Step 4: Under that line, put "maxFPS 30" - Where the "30" is, put your desired framerate. (Multiples of 10 are the most consistent values to enter, but never under 30fps)

Note: This command does not improve performance, but rather smoothens it out, as everyone who's played FEAR games know that the framerate can go from 120 to 35 frequently.

DX10 provides no visual quality boost and is only useful for Anti-Aliasing. Unless you're freaking out because you hate jaggies, then dont worry about DX10. We are still in the first generation of DX10 so we have no idea what to do with it, but since its getting big in the gaming industry, developers are just willing to throw it in so that they make themselves look good, all while knowing we're just going to get mad later. And if any of you guys even say that the 360 version can compare to the PC version, turn off your PC, throw your 360 out the window, turn your PC back on and tell us how relieved you feel once you realized you were a console loving dickhead...