I'm surprised no one else has commented on this part...
SLz wrote:To have a good FPS you will want a constant one.
Doesn't have to be a constant number, just an average that is higher than what you consider playable (generally >30 FPS)
SLz wrote:Higher isnt always better.
Even if you're only getting 2 FPS instead of 1 FPS it's still technically an improvement, albeit a minor one.
SLz wrote:If your computer cannot handle a constant 250 fps which would mean it was inbetween 200 and 250 all the time that would be bad. It would slow down
A constant frame rate is nice, but you're ridiculously overestimating smooth frame rates.
Basically what I'm saying is 200+ FPS is
not bad and you would not be able to identify a slow down between 250 and 200 frames per second (just think about how fast that is - for a second :wink

.
SLz wrote:also you cant jump as far if your fps isnt constant.
What does jumping distance have to do with this?
SLz wrote:So lets say your computer can with-hold a constant 125 fps. To cap it at 125 in the BF2 Console you need to type "game.lockfps 125" (without the "").
Now press enter to send the command to BF2 console and now your FPS is capped at 125.
There's no point in restricting your max FPS below what you can actually achieve, if you really want a more constant frame rate turn on VSync (it'll make a lot more difference above 60fps anyway).