300fps and beyond!

[Crow_Nest]

Its not 90, way above that i think.

[GoJiTa]

Unless they changed the quake3 engine a lot, then the max you can get is 999fps... 1000fps crashes the game, or at least it crashed quake3.

[Andy867]

Jedi Academy has a default value of 85 FPS as being the cap. Now there are ways to uncap it, like set com_maxFPS 300 or 999 or whatever, but that just means it will go above that, although I heard that Raven Software staff said that going above that cap creates a chugging problem since the engine wasnt designed to go higher than like 120 or so.

[lukeskywalker1]

I defragged my HD and now im abole to reach 60 in some areas in JK2. but my 56k slows me down to about 40 max on MP.

[GoJiTa]

Originally posted by Andy867

Jedi Academy has a default value of 85 FPS as being the cap. Now there are ways to uncap it, like set com_maxFPS 300 or 999 or whatever, but that just means it will go above that, although I heard that Raven Software staff said that going above that cap creates a chugging problem since the engine wasnt designed to go higher than like 120 or so.

Well I don't see any problems when playing above their default fps cap. I play with 125fps for the extra (marginally extra) jump height units you get from that framerate. I get absolutely no 'chugging' problem with that framerate. Some framerates have always been considered 'buggy' in quake3 and this will surely be the same for jka. Of the ones I know, framerates of 200-250fps have performance issues, and also 500+fps causes problems. Perhaps this is what they were referring to.

 

-edit-

 

Also when changing com_maxFPS, there are some values that 'don't work', by that I mean you can set them, but they won't cap the fps to that exact number, I have noticed when doing that you sometimes get strange fps lag.

 

"Q3 measures frame time in an integer number of milliseconds. This means that there are only certain frame rates that it can hit... specifically, frame rates of 1000 / N, where N is an integer number of milliseconds. Given this, you can find viable frame rates by varying N."

 

There are only certain numbers that should be used for com_maxFPS, because the engine is only capable of hitting certain framerates. I would assume that using values that can't be hit might create some sort of problem.