[Lightspeed]

Shouldn't be too hard to implement, but would be pretty useful:

-fps_cap XX

Locks the maximum FPS to any given number 'XX'.

[Taristin]

...May I ask why?

[SadisticSid]

Completely useless to most people I'd guess - and not that easy to implement either (presumably you'd have to write in a hook somewhere to block the rendering of every xth frame). What on earth would you need it for? Compatibility with some screen capture program? Playtesting missions on a simulated crappy machine?

[StratComm]

My guess is to aleviate the framerate changes (usually from whatever the max is on a particular machine to about half of that) that occur when looking at/away from intensive-graphics objects or backgrounds.  It would be near-impossible to impliment though, and stopping the stutter in the first place would be the way to go.

[Lightspeed]

Well, might be easy since the original game had a limit at 120 FPS anyway, so maybe it's just the matter of hooking it up to a customizeable variable

As for the reason: When running at high refresh rates, it'd be a lot better if you could lock to half of your refresh rate (V_synched at 50% if you want it that way). I.e. run at 40 FPS at 80 Hz. This way, you wouldn't have any stuttering anymore (unless it goes below 40).

The problem is big changes in framerates, which will always result in "stutters" which you cant get rid off unless you max your FPS all the time - or keep it stable by locking it down.

[StratComm]

The limit of 120 is somewhat machine-hardcoded though.  It's the same in FSO without Vsync, there's no way to get it over 120.  So it's not like all you'd have to do is find that setting and change it to a user-defined variable.

[Lightspeed]

Since Kazan could simply "remove" the cap, I guess it IS some kind of rendering limitation set to that value.

We're not talking about V_synch here, but about an actual FPS limitation.

[Flipside]

I think it can be changed, and I think it's a good idea to be honest. Just because the graphics card CAN run at 120fps, it is still taking work from the CPU in generating those frames iirc.

Capping it off would actually allow more other stuff to go on in the CPU with the idle time