Jump to content

com_maxfps cap 240 or 125?


Recommended Posts

Hi there.  

 

I used to play a lot and have recently taken up interest in playing again.  I used to play with com_maxfps 125, because that's what every guide said was best for the Q3 engine as far as jumps and what-not, but I now have a 240hz monitor and was wondering if I would be able to cap at 240fps or above without suffering from some kind of engine bug or decrease in optimal jumps/benefits from 125fps.

 

So pretty much, can I com_maxfps 240, or should I just stay at 125?  I have a 980ti, so fps isn't a problem.  Thank you in advance!

Link to comment

There are a lot of weird Q3 fps settings. Your jumping will always be impacted directly by your fps, but if you want similar results to 125, 250 might work (there isn't actually an allowed 240 cap. Below is a layout of available fps locks). A lot of competitive players who focus on combat use 142/166 for lower jumps, though pretty much all competitive strafers use 125 as the standard for jumping. Most values have differing effects. 333 makes your jumps floaty and weightless, for example. 200 is pretty common as well for increased frame rate while still retaining jumps similar to 125, if I recall. it has been a while. 

Simply put: Framerate is a personal preference not for game performance and optimization in JK, but rather, for gameplay optimization. You'd want to pick the one that best performs the task for you. Typically 125 is standard, but you've got a lot of options.
 

 

com_maxFPS

 
This is the maximum client framerate permitted. The only valid values are those which are equal to (1000/x) where x is an integer, as Q3 measures frametimes using millisecond integers. So for example your 125fps comes from (1000/8 = 125). 
 
If you try and set maxFPS to an invalid value, you will get the next higher value.
 
1000/3 = ~333
1000/4 = 250
1000/5 = 200
1000/6 = ~166
1000/7 = ~142
1000/8 = 125
1000/9 = ~111
1000/10 = 100
1000/11 = ~90
1000/12 = ~83
1000/13 = ~76
1000/14 = ~71
1000/15 = ~66
1000/16 = ~62
1000/17 = ~58
1000/18 = ~55

(Pretty sure you can do a framerate of 666 as well so.. not sure if this is entirely accurate, I'd need to run an in-game check to be sure, but I may be wrong. In any case, framerates that exceed 333 pretty much just break things anyway, so it's not advised)

Smoo and syainkn like this
Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...