Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The reason for limiting the framerate 2 frames above your refreshrate is the prerendered frames which is optimally 1.X frames and therefore limiting it to 2 frames above will give you the actual refreshrate taking the prerendered frames out of the equation.
Ahh right. So thats why the frames are always a couple below the setting. Thanks, useful to know.
In your opinion, is it better to match the frames or run higher FPS if you can?
frametimes are worse uncapped than capped at refresh in QC , there's numerous threads on reddit about it over the course of 1 year.
I dont belive its input lag I believe its just less accurate frames show so you feel it in your hand.
I would cap at 250 if anything, I certainly wouldnt cap below 200, unless 60hz
in order to stop tearing you'll need a synchronisation. bad: vsync because of input lag, better gsync.
with high hz monitors tearing gets less noticable because you will see those teared frames for a very short time only.
btt: try capping your frames to a value which gives you less fluctuating fps.