Originally posted by Vice
Next to Screen Mode, select one of the 'Max Vsync' modes to unbind the framerate cap.
Thanks to you and Marvin for pointing that out. I had indeed missed it. However, as this screenshot shows it doesn't seem to have much an effect:
http://i47.tinypic.com/11vpg7t.png
(FPS in top-left corner, and yeah, this is after restarting the game.)
Originally posted by Vice
The functional reasons many developers do this (only by default as you can usually unbind it as with this game) can relate to establishing a stable max target framerate for multiplayer object movement prediction, timer calculations, consistent input sampling, reduction of artifacts/tearing, avoid FPS spiking (jerky movement when aiming in FPS's, jumpy object movement, etc), etc. Some games even cap the framerate without the option to change it. On many systems, it's not much of an issue and you can remove any such binding and still get a pretty stable framerate. But on many others (with systems less powerful than yours), the stability and consistency offered by a target maximum can make things smoother and more accurate overall. What is 'good' for you or someone else is subjective, so that's why there is the option to set it to whatever you want. Player tolerances for framerate consistency vary as much as tolerances for maximum FPS, so with settings like that, it's a good idea to support both modes, regardless of which one is default.
Wow. You make some pretty good points. I'm very sensitive to low framerate, but never imagined that people might be bothered by changes in it. Thanks for the detailed answer.
(Though, please consider adding support for optional hardware mouse cursor for the ui on future projects.
)
I'd really like to understand the reasoning that drivers developers to do this.
From the Readme ...
